ASP.NET Code Generator

Labels
AJAX(112) App Studio(7) Apple(1) Application Builder(245) Application Factory(207) ASP.NET(95) ASP.NET 3.5(45) ASP.NET Code Generator(72) ASP.NET Membership(28) Azure(18) Barcode(2) Barcodes(3) BLOB(18) Business Rules(1) Business Rules/Logic(140) BYOD(13) Caching(2) Calendar(5) Charts(29) Cloud(14) Cloud On Time(2) Cloud On Time for Windows 7(2) Code Generator(54) Collaboration(11) command line(1) Conflict Detection(1) Content Management System(12) COT Tools for Excel(26) CRUD(1) Custom Actions(1) Data Aquarium Framework(122) Data Sheet(9) Data Sources(22) Database Lookups(50) Deployment(22) Designer(177) Device(1) DotNetNuke(12) EASE(20) Email(6) Features(101) Firebird(1) Form Builder(14) Globalization and Localization(6) How To(1) Hypermedia(2) Inline Editing(1) Installation(5) JavaScript(20) Kiosk(1) Low Code(3) Mac(1) Many-To-Many(4) Maps(6) Master/Detail(36) Microservices(4) Mobile(63) Mode Builder(3) Model Builder(3) MySQL(10) Native Apps(5) News(18) OAuth(9) OAuth Scopes(1) OAuth2(13) Offline(20) Offline Apps(4) Offline Sync(5) Oracle(11) PKCE(2) Postgre SQL(1) PostgreSQL(2) PWA(2) QR codes(2) Rapid Application Development(5) Reading Pane(2) Release Notes(183) Reports(48) REST(29) RESTful(29) RESTful Workshop(15) RFID tags(1) SaaS(7) Security(81) SharePoint(12) SPA(6) SQL Anywhere(3) SQL Server(26) SSO(1) Stored Procedure(4) Teamwork(15) Tips and Tricks(87) Tools for Excel(2) Touch UI(93) Transactions(5) Tutorials(183) Universal Windows Platform(3) User Interface(338) Video Tutorial(37) Web 2.0(100) Web App Generator(101) Web Application Generator(607) Web Form Builder(40) Web.Config(9) Workflow(28)
Archive
Blog
ASP.NET Code Generator
Monday, June 16, 2014PrintSubscribe
Deployment: Installing Report Viewer 2012

If you have enabled dynamic and static reports for the app, then the Reports menu option is available in the user interface.

Report menu button in the local app.

Selecting any report option will cause the app to produce a PDF, TIFF, Excel, or Microsoft Word document with reporting data.

The various default reporting options.

If Report Viewer is not installed on the machine, any attempt to start the application will display the error message below stating that “Could not load file or assembly Microsoft.ReportViewer.WebForms…”.

Error message displayed when Report Viewer is not installed.

If you do not need reporting or have enabled it by mistake, then select your project in the app generator, choose Settings, select Reporting, and uncheck “Enable dynamic and static reports in my application”. Click Finish to regenerate the app. You may also consider refreshing all controllers to remove the reporting actions from the user interface.

If you do need built-in reporting in your app, then you need to install Microsoft Report Viewer on your deployment machine.

You will need the following files. It is advisable to download them on your personal machine and then copy them onto the server over Remote Desktop Connection (RDC).

  1. Microsoft Report Viewer 2012 Runtime
  2. Microsoft Web Platform Installer

Connect to your server via RDC. Copy the files into the Downloads folder of the server.

Installing SQL Server SQL Types

If SQL Server is not present on the server, then you will need to install Microsoft SQL Server 2012 CLR Types component.

Execute the Web Platform installer file by double-clicking on the “wpilauncher” file.

Executing the Web Platform Installer launcher executable.

When installation is complete, the Web Platform Installer will open. In the search box, type in “CLR” and hit Enter on your keyboard.

Installing MS System CLR types for SQL Server using Web Platform Installer 5.0.

Press Add next to the first item in the list, then press Install. Accept the license terms to proceed.

Installing MS System CLR types for SQL Server using Web Platform Installer 5.0.

Installing Report Viewer

Switch back to the Downloads folder. Double-click on the “ReportViewer” file.

Installing Microsoft Report Viewer 2012 Runtime.

Press Next, then accept the license to install Report Viewer.

This procedure will need to be done on both your development machine and your server.

Monday, June 16, 2014PrintSubscribe
Deployment: Configuring Application in IIS

Press the Start button on your keyboard, and type in “IIS”. Select “Internet Information Services (IIS) Manager”.

Expand the node in the Connections pane to “Sites / Default Web Site / Northwind”. Right-click, and press “Convert to Application…”.

Converting the Northwind folder to an application in IIS.

You must select the correct application pool depending on the ASP.NET version that you selected when creating the app. Click on the “Select…” button next to Application Pool.

Selecting the application pool for the new application.

Click on the Select button and choose the correct version from the dropdown. Be sure to not select the “Classic” version. Then, press OK to save the application pool.

image

Press OK to in the Add Application window to finish conversion.

Adding the Northwind application in IIS.

Right-click on the new application, and press Manage Application | Browse.

Browsing the new application from IIS.

The application will open in your default browser.

Browsing the application on the hosting server.

Your application has been deployed. The local address for the application is “http://localhost/northwind”.

Full Trust

Note: Applications created with Code On Time generator that have reporting enabled will add a line in the web.config file of your project that requires full trust on the server. This will ensure high performance when generating reports. If you do not permit full trust to the application, then you will encounter an error stating “That assembly does not allow partially trusted callers”. To disable the requirement for full trust, open the Project Wizard and switch to the Web Server page. Paste the following into the Web.Config modification instructions.

Delete: /configuration/system.web/trust
<nothing/>

Then proceed to regenerate and redeploy the app.

Monday, June 16, 2014PrintSubscribe
Deployment: Opening Firewall Ports

If the application is configured to run on your computer, then you can access the app locally as “http://localhost/northwind”.

Visiting a locally accessible web app.

If your application is deployed to a Windows Server, then the firewall rule for external HTTP traffic has been enabled. This occurs when the Web Server (IIS) role is added to the server configuration. You will be able to access your application on external desktop and mobile devices.

If your application is deployed to a Windows 7/8 machine, you will need to enable the firewall rule using the steps below.

Press the Start button on your keyboard, and type in “firewall”. Select “Windows Firewall with Advanced Security” from the result list.

Starting Windows Firewall with Advanced Security configuration tool.

In the left pane, select “Inbound Rules”. Scroll to the bottom of the list and find “World Wide Web Services (HTTP Traffic-In)”. In the right pane, click “Enable Rule”.

Enabling the HTTP port 80 firewall rule.

You will now be able to access your application from external devices.