Iron Speed Designer Installation Guide Version 1.5 Accelerated web application development Updated December 24, 2003 Iron Speed, Inc. 1953 Landings Drive Mountain View, CA 94043 650.215.2200 www.ironspeed.com Copyright 2002, 2003 Iron Speed, Inc. 1
CONTENTS Contents...2 System Requirements...4 Iron Speed Designer...4 Applications Generated by Iron Speed Designer...5 Application Users...7 Running on Microsoft.NET...7 Related Products...8 Microsoft Visual Studio.NET...8 Microsoft Access 2000...8 Before You Begin...9 Gather the Information You Will Need...9 Verify the.net Framework was Installed after Microsoft IIS...9 Verify ASP.NET is Set Up Correctly...10 Installing on a Domain Controller Machine (Windows 2000 Server)...11 Adjusting Security Settings in Machine.config...11 Installing Iron Speed Designer...14 Installing Iron Speed Designer...14 Running Multiple Instances of Iron Speed Designer...14 Upgrading Iron Speed Designer...16 Upgrading from Version 1.4...16 Uninstalling Versions 1.3.7 and 1.3.8...16 Migrating from Version 1.3.8 and Earlier...16 Troubleshooting Installation Problems...17 File or assembly name xxx.dll, or one of its dependencies...17 HTTP Error 403 Forbidden. You are not authorized to view this page...17 Potentially dangerous XML...17 Unable to authenticate user...17 Unable to make the session state request...18 Unrecognized attribute 'validaterequest'...19 Appendix A: Configuring Database Authentication for Iron speed designer...21 Using Windows Authentication...21 Case 1: Microsoft SQL Server is installed on the local machine...22 Case 2: Microsoft SQL Server is installed on a remote machine...23 Using Microsoft SQL Server Authentication...23 Page 2
Appendix B: Switching Between.NET Framework 1.0 and 1.1...25 Switching to.net Framework V1.1...25 Switching to.net Framework V1.0...26 Restarting ASP.NET State Service...26 Appendix C: Iron Speed Personal Web Server...29 Personal Web Server...29 Security...29 Virtual Directory Configuration...29 Using Microsoft Internet Explorer...30 Using Microsoft Internet Information Server (IIS)...31 Technical Support...32 Index...33 Page 3
SYSTEM REQUIREMENTS Installing Iron Speed Designer takes about 20 minutes. There is very little expertise required to install Iron Speed Designer except for knowing the locations of your database and email server. Iron Speed Designer Iron Speed Designer can be installed on either a Microsoft Windows 2000 Professional or a Microsoft Windows XP Server. The installed machine must have the Microsoft.NET Framework. If you need to modify the code generated by Iron Speed Designer, you will also require appropriate code and web page editing tools, such as Microsoft Visual Studio.NET, and the.net SDK (which comes with Visual Studio.NET). Component Server operating system.net Framework Minimum Requirement Windows 2003 Server Windows XP Professional, Service Pack 1 or later Windows 2000 Professional Windows 2000 Server, Service Pack 3 or later Windows 2000 Advanced Server, Service Pack 3 or later Windows 2000 Datacenter Server, Service Pack 3 or later Version 1.1 (Windows 2000 Server, Windows XP Professional) Version 1.0, Service Pack SR2 See Appendix B: Switching Between.NET Framework 1.0 and 1.1 for further details on switching from one version of the.net Framework to the other. You can download Version 1.0 of.net Framework from the following websites: http://msdn.microsoft.com/library/default.asp?url=/downloads/list/netdevframework.asp http://msdn.microsoft.com/netframework/downloads/default.asp http://msdn.microsoft.com/netframework/downloads/howtoget.asp.net SDK Web server Application Database If you intend to modify the code generated by Iron Speed Designer. Microsoft IIS 5.0 or later Microsoft SQL Server 2000, Service Pack 3 or later Microsoft SQL Server 7, Service Pack 4 or later MSDE 2000, Service Pack 3 or later (for evaluation purposes) Page 4
Component Minimum Requirement The default MDAC (Microsoft Data Access Components) driver installed with Windows 2000 is not sufficient to run Iron Speed Designer. Iron Speed Designer requires MDAC Version 2.6 or above, and the default driver included in Windows 2000 is Version 2.5. This driver is automatically updated if you have Microsoft SQL Server 2000 or MSDE 2000 installed on your machine with the latest service packs. In the event you do not have the latest version of the driver, you can download Version 2.7 of this driver from: http://www.microsoft.com/data/ Note: Iron Speed Designer has not yet been certified to work with the upcoming Microsoft SQL Server 64 bit edition. Iron Speed Designer Database Web browser Integrated Development Environment Microsoft JET 4.0, service pack 6 or later Microsoft Internet Explorer 6.0 or later Microsoft Visual Studio.NET (optional) (if you intend to modify or extend the generated source code) Iron Speed Designer requires a minimum of 256 MB of memory and 512MB is recommended. There are additional requirements if the development machine also has a database (e.g., Microsoft SQL Server) installed. Approximately 40 MB of disk space is required. We recommend installing Iron Speed Designer on the desktop machine of each individual developer. However, Iron Speed Designer can be installed on a server machine, and multiple developers can develop multiple applications using the same server. (Please note that each developer will require a separate license to use Iron Speed Designer). To modify the source code generated by Iron Speed Designer, you must be able to access the hard drive where the generated code is stored. Applications Generated by Iron Speed Designer Once the application is ready for testing, you can copy the generated application to another server. Detailed instructions for deploying applications to test and production servers are in the companion manual, Iron Speed Designer Application Developers Guide. Page 5
Component Server operating system.net Framework Minimum Requirement Windows 2003 Server Windows XP Professional, Service Pack 1 or later Windows 2000 Professional, Service Pack 3 or later Windows 2000 Server, Service Pack 3 or later Windows 2000 Advanced Server, Service Pack 3 or later Windows 2000 Datacenter Server, Service Pack 3 or later Version 1.1 (Windows 2000 Server, Windows XP Professional) Version 1.0, Service Pack SR2 The.NET Framework Redistributable version is sufficient to run applications generated by Iron Speed Designer. If you wish to recompile your application on your production server, you will, however, need the.net SDK. See Appendix B: Switching Between.NET Framework 1.0 and 1.1 for further details on switching from one version of the.net Framework to the other. You can download Version 1.0 of.net Framework from the following websites: http://msdn.microsoft.com/library/default.asp?url=/downloads/list/netdevframework.asp http://msdn.microsoft.com/netframework/downloads/default.asp http://msdn.microsoft.com/netframework/downloads/howtoget.asp Web server Database Microsoft IIS 5.0 or later Microsoft SQL Server 2000, Service Pack 3 or later Microsoft SQL Server 7, Service Pack 4 or later The default MDAC (Microsoft Data Access Components) driver installed with Windows 2000 is not sufficient to run applications generated by Iron Speed Designer. Iron Speed Designer requires MDAC Version 2.6 or above, and the default driver included in Windows 2000 is Version 2.5. This driver is automatically updated if you have Microsoft SQL Server 2000 or MSDE 2000 installed on your machine with the latest service packs. In the event you do not have the latest version of the driver, you can download Version 2.7 of this driver from: http://www.microsoft.com/data/ Note: Applications generated by Iron Speed Designer have not yet been certified Page 6
Component Minimum Requirement to work with the upcoming Microsoft SQL Server 64 bit edition. Iron Speed base classes You will need to install the Iron Speed Designer base classes on any server running your generated application. (Note: there are no additional run-time licenses or fees required.) The Iron Speed base classes include a set of server side controls and data validation classes. Full source code is provided. Applications generated by Iron Speed Designer will not run on these operating systems because the Microsoft Internet Information Server (IIS) is not available on them: Windows XP Home Edition Windows XP Tablet PC Edition Windows XP Embedded Windows XP Media Center Edition Application Users None of the end-user desktops require any extensions or changes to run applications generated by Iron Speed Designer. In fact, Iron Speed Designer generated applications are accessible through any reasonably contemporary web browser, regardless of machine, including Windows, Mac, and Unix machines. Component Web browser Minimum Requirement Microsoft Internet Explorer 5.5 and above Netscape 6.2 and above JavaScript (a.k.a. ECMAScript) must be enabled Cookies must be enabled Running on Microsoft.NET The Microsoft.NET Framework is a freely downloadable extension to the Windows 2000 Server. If you already have a Windows 2000 or Windows XP server, you can upgrade it to run.net Framework freely and easily. No additional software or hardware is needed for the applications generated by Iron Speed Designer to run on.net. If you like, you can run the.net Framework on only the hardware that runs the applications generated by Iron Speed Designer. You do not need to convert all of your servers to run this framework. Page 7
None of the end-user desktops require any extensions or changes to run Iron Speed generated applications. In fact, Iron Speed Designer generated applications are accessible through any reasonably contemporary web browser, regardless of machine, including Windows, Mac, and Unix machines. Related Products Microsoft Visual Studio.NET Iron Speed Designer uses VBC to compile your application s Visual Basic.NET files. VBC is a command line Visual Basic compiler that is part of the.net Framework SDK. Iron Speed Designer does not require you to use any particular integrated development environment, such as Microsoft Visual Studio.NET. However, Iron Speed Designer creates and updates certain files (e.g. VBPROJ) that make it easier for Visual Studio. NET users to customize generated applications. Microsoft Access 2000 Microsoft Access 2000 supports one of two back-end technologies: MSDE and Microsoft Jet. With the release of Microsoft Access 2000, users and developers will have the choice of two data engines in the product: an improved version of the existing Access engine, called Microsoft Jet, or the Microsoft Data Engine (MSDE), which is compatible with Microsoft SQL Server 7.0. The default data engine for Microsoft Access is Jet. While Iron Speed Designer does not provide support for Jet at this time, it does support MSDE-based support for Microsoft Access. Page 8
BEFORE YOU BEGIN Gather the Information You Will Need Before installing Iron Speed Designer, you will need to gather the following information: Component Microsoft IIS Server root directory Administrative privileges You will need Microsoft IIS web server administrative privileges to install Iron Speed Designer. This allows Iron Speed Designer to configure virtual directories in Microsoft IIS for the generated applications. Contact your system administrator if you need administrative privileges for your Microsoft IIS web server. Microsoft SQL Server Database server name Administrative privileges SMTP Server (Optional) Email server name Default sender address Iron Speed Designer creates and updates a database that stores information about the applications you create. During installation, Iron Speed Designer logs in to your Microsoft SQL Server in order to create its tracking database. Accordingly, you will need administrative privileges to your Microsoft SQL Server database in order to install Iron Speed Designer. The applications generated by Iron Speed Designer have built-in email capabilities allowing application users to be notified via email for a variety of functions, including lost password notification. The SMTP server must be configured to accept relays from the machine where your application is installed. Verify the.net Framework was Installed after Microsoft IIS In order for Iron Speed Designer to install and run properly, the.net Framework must be installed after Microsoft IIS is installed. If this is not the case for your machine, Microsoft provides the aspnet_regiis utility program to uninstall and then reinstall the.net Framework. Its purpose is to ensure that ASP.NET is set up properly and otherwise manage the.net installation. Specifically, aspnet_regiis: Defines the ASP.NET user account under which Microsoft IIS runs. Registers all of the ASP.NET components with Microsoft IIS. Page 9
Defines the ASP.NET State Service that is used by Microsoft IIS when running.net applications. Copies the common ASP.NET files to their proper place. Associates particular web applications with their correct versions of.net. Run the following command sequence to set up your Microsoft IIS web server properly. (aspnet_regiis is a utility provided as part of the Microsoft.NET framework.) aspnet_regiis -u aspnet_regiis -i The "-u" flag uninstalls the current version of the.net Framework. The "-i" flag installs the current version of the.net Framework. Additional information can be found at: http://support.microsoft.com/default.aspx?scid=kb%3ben-ujs%3b306005 Finally, set the.net Framework to run automatically: Go to: Control Panel Administrative Tools Services Locate "ASP.NET State Service". Set Startup type to: "Automatic" Click "Start", if the "ASP.NET State Service" is not started. Click OK. Verify ASP.NET is Set Up Correctly Iron Speed Designer requires access to a Microsoft SQL Server database in order to be installed and to run after installation. Accordingly, you will need to provide login information sufficient for the Iron Speed Designer installation program to connect to and log into a Microsoft SQL Server database and to create several tables Iron Speed Designer requires to operate. All web applications in the.net environment, including Iron Speed Designer, run by default under a Windows user account named <local machine>\aspnet. This ASPNET user is a local machine account that has limited privileges. If Microsoft SQL Server is installed on your local machine, it is possible to create a Microsoft SQL Server login account for the ASPNET user, allowing Iron Speed Designer to connect to Microsoft SQL Server using "Windows authentication". If, however, Microsoft SQL Server is running on a remote machine, it is not possible to create a login Page 10
account for the <local machine>\aspnet user because the ASPNET user is not recognized as a valid domain account. (ASPNET is a local machine account only.) In this case, you must log into Microsoft SQL Server using Microsoft SQL Server Authentication. Installing on a Domain Controller Machine (Windows 2000 Server) If you are running Iron Speed Designer on a Windows 2000 server that is also a domain controller, you must make sure that ASP.NET is set up correctly. Follow the instructions at the link below to setup ASP.NET correctly on a Windows 2000 machine that is a domain controller: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wss/wss/_exch2k_running_asp_net_on_a_dc.asp http://support.microsoft.com/default.aspx?scid=kb%3ben-ujs%3b318465 Alternatively, you may use another Windows 2000 Server that is not setup as a domain controller. Adjusting Security Settings in Machine.config Problems can be caused by the security settings in the ASP.NET user account on the machine itself. One reason for this is that your Windows 2000 machine is set up as a domain controller. This Microsoft support link describes the problem and its resolution: http://support.microsoft.com/default.aspx?scid=kb;en-us;q315158 Page 11
The solution is to set the username attribute to SYSTEM in the <processmodel> section of the Machine.config file. Step 1: Locate your machine.config file. For example: C:\<WINDOWS-DIRECTORY>\Microsoft.NET\Framework\v1.0.3705\CONFIG Step 2: Change the following attributes in the processmodel element to use a Windows domain user. username password Please note that the password of the Windows domain user needs to be in clear text (not encrypted). Open the Machine.config file and search for the string processmodel. The line you should change looks like: <processmodel enable="true" timeout="infinite" idletimeout="infinite" shutdowntimeout="0:00:05" requestlimit="infinite" requestqueuelimit="5000" restartqueuelimit="10" memorylimit="60" webgarden="false" cpumask="0xffffffff" username="system" password="autogenerate" loglevel="errors" clientconnectedcheck="0:00:05" comauthenticationlevel="connect" comimpersonationlevel="impersonate" responserestartdeadlockinterval="00:09:00" responsedeadlockinterval="00:03:00" maxworkerthreads="25" maxiothreads="25"/> username="[user]" is the Microsoft Windows user name used to run the process. If a domain is not specified, the current machine name is assumed to be the domain name. There are several special users: "SYSTEM": run the process as a local system (high privilege administrator) account. "Machine": run as the process as a low privilege user account named "ASPNET". Page 12
password="[autogenerate password]" is the password of the designated Microsoft Windows user. Specify "AutoGenerate" for special users (SYSTEM and machine). Page 13
INSTALLING IRON SPEED DESIGNER Installing Iron Speed Designer 1. Using your web browser, go to the Iron Speed Designer download page: http://www.ironspeed.com/download.asp. 2. Click the "click here" link under the "Download Designer" section, and save the file to your hard disk. A convenient location is your Desktop, though it may be saved anywhere on your hard disk. 3. Run the Iron Speed Designer Installer program by double-clicking the "Iron Speed Designer Installer.exe" icon. 4. Follow the instructions in the installation program to properly install Iron Speed Designer. Running Multiple Instances of Iron Speed Designer Iron Speed Designer requires its application URL to be http://<server>/designer. If you have two versions of Iron Speed Designer installed on the same machine, only one of them can be configured to use this URL, so you can only run that version. By default, the most recent version you installed will be assigned this URL, so you cannot run an older version without reassigning the URL to the older version. Suppose you have two versions installed in the following directories: C:\Program Files\IronSpeedDesigner142 (version 1.4.2) C:\Program Files\IronSpeedDesigner143 (version 1.4.3) By default, when you run http://<server>/designer it will run version 1.4.3 because that is the one that was most recently installed. In order to run version 1.4.2, you will have to change the virtual directory configuration to point to C:\Program Files\IronSpeedDesigner142. This can be done as follows: Step 1: Bring up the Internet Information Services manager: Control Panel -> Administrative Tools -> Internet Information Services Step 2: Navigate to the virtual directory called "Designer" Step 3: Right click and bring up the Properties dialog Step 4: In the Virtual Directory tab, modify the Local Path to point to the directory where the version you want to run is installed. Page 14
Step 5: Save changes. Run http://<server>/designer and you will be running the previous version. Page 15
UPGRADING IRON SPEED DESIGNER When upgrading to a new version of Iron Speed Designer, you should uninstall the old version first. Uninstalling Iron Speed Designer will not delete your applications or any generated components. As a safety precaution, we recommend first making a backup copy of your c:\program Files\Iron Speed Designer directory (or equivalent) prior to uninstalling Iron Speed Designer. Upgrading from Version 1.4 There is no special conversion or migration required to upgrade applications generated by Iron Speed Designer Version 1.4. You can easily import existing applications generated by Version 1.4 into the new Iron Speed Designer using the Import button on the Application tab in Iron Speed Designer. Uninstalling Versions 1.3.7 and 1.3.8 Uninstalling Iron Speed Designer Versions 1.3.7 and 1.3.8 will completely remove all Iron Speed Designer and Run Time Library files from your computer. It will not remove any applications that you have created with Iron Speed Designer, but those applications cannot be run without the Iron Speed Run Time Library installed. Therefore, before uninstalling Iron Speed Designer, it is recommended that you make a backup of the Platform and/or ApplicationThemes folders if you have made any additions or customizations to either of them. Migrating from Version 1.3.8 and Earlier Applications created with Iron Speed Designer Version 1.3.8 are not completely compatible with Iron Speed Designer Version 1.4. For migrating applications created with version 1.3.8 or earlier, you must migrate the application. Before migrating, it is recommended that you make a backup of the application's entire folder. Migration will delete and modify some of your application's files, so you should not migrate an application until you are ready to totally regenerate the application's files. Page 16
TROUBLESHOOTING INSTALLATION PROBLEMS File or assembly name xxx.dll, or one of its dependencies After installing and running Iron Speed Designer, you may see this error message: File or assembly name xxxxxxxx.dll, or one of its dependencies, was not found. This occurs when the.net Framework is not properly registered under Microsoft IIS, generally because the.net Framework was installed before Microsoft IIS. Run this command line utility provided by Microsoft to fix this problem: aspnet_regiis I HTTP Error 403 Forbidden. You are not authorized to view this page Your.NET Framework is not running. You must set it to run automatically after installing it. See the section Verify the.net Framework was Installed after Microsoft IIS in this Guide for details on how to properly install and configure the.net Framework so that it runs automatically. Potentially dangerous XML If you see warning messages regarding "potentially dangerous" XML, it means that applications need to run under.net Framework version 1.1. If you have both.net Framework version 1.0 and.net Framework 1.1 installed on your machine, the Iron Speed Designer installation program assumes that you will be running applications using.net Framework version 1.1. This assumption may not always be correct. Even though.net Framework version 1.1 is installed, your system (Microsoft IIS) may be configured to run applications under.net Framework version 1.0. See Appendix B: Switching Between.NET Framework 1.0 and 1.1 for further details on changing the Web.config file. Unable to authenticate user After installing Iron Speed Designer, you receive the following message when attempting to log into Iron Speed Designer: "Unable to authenticate user. Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. Page 17
Please grant SQL Server login privileges and add the System Administrators role to the user on the '<servername>' instance of SQL Server." The problem is caused by the absence of configuration information that prevents Iron Speed Designer from connecting to the Microsoft SQL Server database. See Appendix A: Configuring Database Authentication for Running Iron Speed Designer. Unable to make the session state request Your ASP.NET State Service is not running. Follow these steps to automatically run the ASP.NET State Service: Go to: Control Panel Administrative Tools Services Locate "ASP.NET State Service". Set Startup type to: "Automatic" Click "Start", if the "ASP.NET State Service" is not started. Click OK. Page 18
Unrecognized attribute 'validaterequest' Support has been added for.net Framework version 1.1. Microsoft added a new feature in.net Framework 1.1 called Request Validation. By default, each page is checked to see that no raw XML is submitted. Details can be found at: http://www.asp.net/faq/requestvalidation.aspx The Iron Speed Designer installation program checks to see if.net Framework version 1.1 is installed on your machine. If so, the Web.config file of Iron Speed Designer as well as all generated applications are set with the Request Validation feature turned off. We have determined that Request Validation is not required for Iron Speed Designer or generated applications. If you have both.net Framework version 1.0 and.net Framework 1.1 installed on your machine, the Iron Speed Designer installation program assumes that you will be running applications using.net Framework version 1.1. This Page 19
assumption may not always be correct. Even though.net Framework version 1.1 is installed, your system (Microsoft IIS) may be configured to run applications under.net Framework version 1.0. If you see an error that says: Unrecognized attribute 'validaterequest' you may need to change the Web.config file for Iron Speed Designer and the generated applications. See Appendix B: Switching Between.NET Framework 1.0 and 1.1 for further details on changing the Web.config file. Alternatively, if you see warning messages regarding "potentially dangerous" XML, it means that applications need to run under.net Framework version 1.1. Page 20
APPENDIX A: CONFIGURING DATABASE AUTHENTICATION FOR IRON SPEED DESIGNER ASP.NET applications such as Iron Speed Designer and the applications it generates must provide authentication credentials when connecting to Microsoft SQL Server databases. For example, when connecting to a database to link tables in Iron Speed Designer, you are asked to select an authentication mode. You have two options: 1. Windows Authentication. This will use the Microsoft Windows user credentials specified in your.net framework machine.config file. 2. Microsoft SQL Server Authentication. Use the name and password of a specific SQL Server login account. Using Windows Authentication All ASP.NET applications, including Iron Speed Designer, are configured to run as a specific Windows user. This is specified in the.net framework machine.config file. By default, the user account is <local machine>\aspnet. This ASPNET user is a local machine account that has limited privileges. This allows web applications to run as a relatively un-trusted user without administrative privileges so they cannot compromise the integrity of the server. You can check the user configuration in the machine.config file as follows: Step 1: Locate your machine.config file. For example: C:\<WINDOWS-DIRECTORY>\Microsoft.NET\Framework\v1.0.3705\CONFIG Step 2: Search for the string processmodel and look for the username and password attributes. <processmodel enable="true" timeout="infinite" idletimeout="infinite" shutdowntimeout="0:00:05" requestlimit="infinite" requestqueuelimit="5000" restartqueuelimit="10" memorylimit="60" webgarden="false" cpumask="0xffffffff" username="machine" password="autogenerate" loglevel="errors" clientconnectedcheck="0:00:05" Page 21
username="[user]" is the Microsoft Windows user name used when running ASP.NET applications. If a domain is not specified, the current machine name is assumed to be the domain name. There are two special users: "machine": run the process as a low privilege user account named "ASPNET". (This is the default) "SYSTEM": run the process as a local system (high privilege administrator) account. password="[autogenerate password]" is the password of the designated Microsoft Windows user. Specify "AutoGenerate" for special users (machine and SYSTEM). When ASP.NET is running under Microsoft IIS 6 in native mode, the Microsoft IIS 6 process model is used and settings in this section are ignored. Use the Microsoft IIS administrative user interface to configure process identity and cycling for the Microsoft IIS worker process for the desired application. If Microsoft SQL Server is installed on the same machine as your Microsoft IIS web server, you can create a Microsoft SQL Server login account for the configured Windows user, even if that user is the default <local machine>\aspnet user. This allows Iron Speed Designer and the applications it generates to connect to Microsoft SQL Server using "Windows authentication". If, however, Microsoft SQL Server is running on a remote machine, it is not possible to create a SQL Server login account for the <local machine>\aspnet user because the ASPNET user is not recognized as a valid domain user. It is a local machine account only. In this case, you will have to reconfigure ASP.NET to run as a valid domain user instead of the default ASPNET user. Case 1: Microsoft SQL Server is installed on the local machine If your Microsoft IIS web server and your Microsoft SQL Server are running on the same machine, do the following to enable Iron Speed Designer and the applications it generates to connect to Microsoft SQL Server. Step 1: Determine the Windows user ID that is used by ASP.NET applications by checking the machine.config file as described above. By default, this user ID is <local machine>\aspnet. Step 2: Create an account for the user in Microsoft SQL Server Use Enterprise Manager --> Database server --> Security --> Logins If you have not changed the default ASP.NET user, add a <local machine>\aspnet login. If you have changed the default ASP.NET user to a user other than ASPNET, add a login for that user. Step 3: If you are using Iron Speed Designer Enterprise edition, you will have to grant db_owner rights to this user on any databases you plan to reference. This will allow Iron Speed Designer to create stored procedures in those databases. You should now be able to connect from Iron Speed Designer to Microsoft SQL Server using Windows Authentication. Page 22
Case 2: Microsoft SQL Server is installed on a remote machine If your Microsoft SQL Server is running on a different machine than Iron Speed Designer (your Microsoft IIS web server) and you have not changed the default ASP.NET user, you will need to perform additional configuration steps. If you do not, you will get a user not found error when you try to add a Microsoft SQL Server login for the ASPNET user. In particular, you must change the ASP.NET user to a valid domain user by configuring machine.config as follows. Step 1: Locate your machine.config file. For example: C:\<WINDOWS-DIRECTORY>\Microsoft.NET\Framework\v1.0.3705\CONFIG Step 2: Change the username and password attributes in the processmodel element to a valid Windows domain user. See above for a description of the username and password attributes. Step 3: Reset Microsoft IIS or stop the aspnet_wp.exe process in order for your changes to take effect. Step 2: Create an account for the configured user (now a valid domain user) in Microsoft SQL Server Use Enterprise Manager --> Database server --> Security --> Logins Step 3: If you are using Iron Speed Designer Enterprise edition, you will have to grant db_owner rights to this user on any databases you plan to reference. This will allow Iron Speed Designer to create stored procedures in those databases. You should now be able to connect from Iron Speed Designer to Microsoft SQL Server using Windows Authentication. Using Microsoft SQL Server Authentication In order to use Microsoft SQL Server Authentication, your Microsoft SQL Server must be configured to allow this option. This is configured from Microsoft SQL Server Enterprise Manager. To enable Microsoft SQL Server Authentication: Step 1: Start Microsoft SQL Server Enterprise Manager. Step 2: Locate the Microsoft SQL Server you wish to configure. Right-click the server and select Properties. The Properties dialog is displayed. Step 3: In the Properties dialog, select Security. Page 23
Step 5: Select Authentication: SQL Server and Windows or Authentication: Windows and close the dialog. This configures your Microsoft SQL Server. You should now be able to connect from Iron Speed Designer to Microsoft SQL Server using Microsoft SQL Server Authentication. When linking database tables, you must know the specific name and password of the Microsoft SQL Server login that has the appropriate permissions to read and write to the databases you use. Page 24
APPENDIX B: SWITCHING BETWEEN.NET FRAMEWORK 1.0 AND 1.1 After downloading and installing Microsoft.NET Framework 1.1 there are several configuration issues to resolve. 1. Update the Iron Speed Designer Web.config file in the \<Iron Speed Designer>\Designer subdirectory. 2. Update the Web.config files for each of your generated applications. 3. Reset the ASP.NET state service default to automatically run on start-up. For information on the differences between.net Framework 1.0 and 1.1: http://www.gotdotnet.com/team/changeinfo/default.aspx Switching to.net Framework V1.1 We provide two versions of Web.config to make it easy to switch between.net Framework version 1.0 (Web1.0.config) and Version 1.1 (Web1.1.config). To switch to.net Framework version 1.1, do the following: copy...<iron Speed Folder>\Designer\Web1.1.config to...<iron Speed Folder>\Designer\Web.config copy...<iron Speed Folder>\ProjectTemplate\Source\Web1.1.config to...<iron Speed Folder>\ProjectTemplate\Source\Web.config Page 25
For each generated application s \<APP NAME>\Web.config file and \<APP NAME>\Source\Web.config file, add this tag to the <System.web> section: <pages validaterequest="false" /> Note: The application s Web.config file is different from the Iron Speed Designer Web.config file. Switching to.net Framework V1.0 To switch to.net Framework version 1.0, do the following to update the Web.config file in the Designer subdirectory: copy...<iron Speed Folder>\Designer\Web1.0.config to...<iron Speed Folder>\Designer\Web.config copy...<iron Speed Folder>\ProjectTemplate\Source\Web1.0.config to...<iron Speed Folder>\ProjectTemplate\Source\Web.config For each generated application s \<APP NAME>\Web.config file and \<APP NAME>\Source\Web.config file, remove this tag from the <System.web> section: <pages validaterequest="false" /> Note: The application s Web.config file is different from the Iron Speed Designer Web.config file. Restarting ASP.NET State Service Reset ASP.NET state service default to automatic load on start-up. Open the Windows desktop, right-click on My Computer and select Manage. This opens the Computer Management Directory Box. Page 26
In the left-hand navigation pane, open the Services and Applications directory structure and click on Services. The right-hand pane will display all of the available services and their current status. Double click on the ASP.NET State Service to open its properties box and it should open displaying the General tab. On that tab, set the Startup type drop-down box to automatic and if the Service Status is not started, click on the Start button to start the ASP.NET State Service. When this has been done click the Apply and OK buttons and close out the Computer Management Directory Box. Page 27
Page 28
APPENDIX C: IRON SPEED PERSONAL WEB SERVER Personal Web Server Iron Speed Designer's default configuration uses the Iron Speed Personal Web Server to ensure that all operating system environments are supported. You can change the default configuration to use Microsoft Internet Information Server (IIS) if you like as shown below. The Iron Speed Personal Web Server has been developed using the Microsoft.NET Framework Version 1.1. When Personal Web Server is automatically started with Iron Speed Designer is first run. When the Personal Web Server is running, an icon is displayed in the system tray in your operating system. The Personal Web Server installs itself on the first port available starting with port number 8080. There can be only one copy of the Personal Web Server running at a time. Each time the Personal Web Server runs, it finds the first available port, so the port number will change from time to time based on the availability of the ports. Security To protect your computer, the Personal Web Server is built to only respond when it is accessed from the local computer. Remote access from another computer, whether inside or outside the firewall, is disabled at the code level and cannot be turned on through a configuration setting. Moreover, the only port that is used is the selected port, and only when accessed from the same computer. From all other computers, the Personal Web Server behaves as if it does not even exist. Virtual Directory Configuration The Iron Speed Designer Personal Web Server maintains its virtual directory settings in a configuration file. The configuration file is located in: Page 29
<Iron Speed Designer>\PersonalWebServer\PWSApp.exe.config The configuration file contains information about the port currently being used by the Personal Web Server as well as the virtual directory names and locations. <?xml version="1.0" encoding="utf-8"?> <configuration> <appsettings> <add key="portnumber" value="8080" /> <add key="/designer" value="c:\program Files\Iron Speed Designer\Designer" /> <add key="/testapp" value="c:\applications\testapp" /> </appsettings> </configuration> The port number will be the first available open port equal to or greater than 8080. When a new port is selected, the configuration file is updated. The virtual directory settings are specified in the file relative to the root directory of the server. For example, /Designer is Iron Speed Designer s virtual directory and points to the C:\Program Files\Iron Speed Designer\Designer folder. Using Microsoft Internet Explorer Iron Speed Designer can be used either as a stand-alone application or from Microsoft Internet Explorer. When using the Microsoft Internet Explorer, you can either use Iron Speed Personal Web Server or the Microsoft Internet Information Server (IIS). The different configurations are shown below: Iron Speed Designer Stand-alone Application Iron Speed Designer running under Internet Explorer Iron Speed Personal Web Server Microsoft Internet Information Server (IIS) Page 30
When using Iron Speed Designer with Internet Explorer, you can use the following URL: http://localhost:8080/designer The port number should match the port that is being used by the Personal Web Server. Using Microsoft Internet Information Server (IIS) Iron Speed Designer is fully compatible with Microsoft Internet Information Server (IIS). If Microsoft IIS is installed and running on your computer, you can access Iron Speed Designer from the following URL using Microsoft Internet Explorer: http://localhost/designer The Iron Speed Designer installer automatically creates a virtual directory for designer under Microsoft IIS. In the event the virtual directory cannot be created because the currently logged in account does not have the appropriate security settings, the virtual directory will need to be created before Iron Speed Designer can be started. You can also use Microsoft IIS to run your applications by using a similar URL http://localhost/<application_name> The Iron Speed Designer New Application Wizard automatically creates a virtual directory for the application under Microsoft IIS when the application is first created. In the event the virtual directory cannot be created because the currently logged in account does not have the appropriate security settings, the virtual directory would need to be created before the generated application can run. You will also need to create the virtual directory if the application is moved from one computer to another. Page 31
TECHNICAL SUPPORT Should you have any difficulty installing or using Iron Speed Designer, please contact us for technical support. web-based support: www.ironspeed.com/support 650-215-2230 M-F 8am to 6pm Pacific Time Page 32
INDEX.NET framework System requirements... 4, 6.NET Framework 1.0 Web.config... 26.NET Framework 1.1 Web.config... 26.NET SDK System requirements... 4 Adjusting Security Settings in Machine.config... 12 Application Users... 8 Applications Generated by Iron Speed Designer... 6 ASP.NET Session state service... 19 Setup... 11 State service... 26, 28 Authentication Windows... 22 Base classes System requirements... 7 Case 1 Microsoft SQL Server is installed on a remote machine... 24 Microsoft SQL Server is installed on the local machine... 23 Configuring Database Authentication for Running Iron Speed Designer... 22 Database Authentication... 22 System requirements... 5, 7 Domain controller machine... 12 Enterprise Manager configuration... 24 File or assembly name xxx.dll, or one of its dependencies... 18 Gather the Information You Will Need... 10 HTTP Error 403 Forbidden. You are not authorized to view this page... 18 Installing Iron Speed Designer... 15 Installing on a Domain Controller Machine (Windows 2000 Server)... 12 Integrated development environment System requirements... 5 Iron Speed Designer database... 5 JavaScript System requirements... 8 Machine.config Security settings...12 Microsoft.NET...8 Microsoft.NET framework Installation...10 Microsoft Access 2000...9 Microsoft IIS web server...10 System requirements...5 Microsoft Internet Explorer System requirements...5 Microsoft JET database System requirements...5 Microsoft SQL Server Login authentication...22 Priviledges...10 Security configuration...24 System requirements...5 Microsoft SQL Server Enterprise Manager...24 Microsoft Visual Studio.NET...8 System requirements...5 Microsoft Windows Server operating system requirements...4 Migrating from Version 1.3.8 and Earlier...17 Personal Web Server...30 Potentially dangerous XML...18 Running on Microsoft.NET...8 Security Machine.config settings...12 Security Windows authentication...22 Server operating system System requirements...4, 6 Session state service...19 SMTP Server...10 State service...26, 28 Switching Between.NET Framework 1.0 and 1.1...26 System requirements.net framework...4, 6.NET SDK...4 Application database...5 Base classes...7 Cookies...8 Database...7 Integrated development environment...5 Iron Speed Designer database...5 JavaScript...8 Page 33
Server memory... 5 Server operating system... 4, 6 Web browser... 5, 8 Web server... 5, 7 System Requirements... 4 Application users... 8 Generated applications... 6 Iron Speed Designer... 4 Technical Support... 32 Unable to authenticate user... 18 Unable to make the session state request... 19 Uninstalling Versions 1.3.7 and 1.3.8... 17 Unrecognized attribute validaterequest... 20 Upgrading from Version 1.4... 17 Upgrading Iron Speed Designer...17 Using Internet Explorer...30 Using Microsoft Internet Information Server (IIS)...31 Using Microsoft SQL Server Authentication...24 Using Windows Authentication...22 Verify ASP.NET is Set Up Correctly...11 Verify the.net Framework was Installed after Microsoft IIS...10 Visual Studio.NET...8 Web browser...5 System requirements...8 Web server...7 System requirements...5 Page 34