Matrix. If you have problems during installation, refer to Troubleshooting Problems with Microsoft Web Platform Installer. How to Publish Applications. See Step by Step Instructions for Publishing Applications. Changes and Issues. Web. Matrix 1. 0 Installation Issues. Issue Web. Matrix 1. Microsoft. NET Framework 4. The. NET Framework version 4 is required for Web. Matrix. In certain cases, the Web. Matrix 1. 0 installer will let you try to install on a platform that is not part of the supported configuration set. In particular, Windows Vista without the SP1 update will let you begin the installation of Web. Matrix, but the. NET Framework 4 component will fail and block your installation. Workaround. Install on a supported platform, which includes Windows 7. MSDN Magazine Issues and Downloads. Read the magazine online, download a formatted digital version of each issue, or grab sample code and apps. This is a problem that has been plaguing my windows for quite some time and I have been unable to fix, I feel that as tho a full wipe will be necessary, but I really. Microsoft Data Access Components MDAC also known as Windows DAC is a framework of interrelated Microsoft technologies that allows programmers a uniform and. Driver Verifier is available in all versions of Windows starting with Windows 2000. Each version introduces new features and checks for finding bugs in Windows drivers. DiskPart is a textmode command interpreter in Windows Vista, Windows XP, and the Windows Server 2003 family. This tool enables you to manage objects disks. Windows Server 2. Windows Server 2. R2. Windows Vista SP1 or later. Windows XP SP3. Windows Server 2. SP2. Issue Cannot install Web. Matrix 1. 0 if Microsoft Visual Studio 2. X4AzXuT' alt='Microsoft Visual Studio The Parameter Is Incorrect Vista' title='Microsoft Visual Studio The Parameter Is Incorrect Vista' />Microsoft Visual Studio 2. SP1. Workaround. Install Microsoft Visual Studio 2. SP1 from the Microsoft Download Center. Issue Some assemblies for SQL Server Compact 4. GACThe managed assemblies for SQL Server Compact 4. GAC when you install SQL Server Compact 4. CLFParameters_20080326173935.PNG' alt='Microsoft Visual Studio The Parameter Is Incorrect Vista' title='Microsoft Visual Studio The Parameter Is Incorrect Vista' />NET Framework 3. SP1 Client Profile installed. The managed assemblies that are not installed in the GAC are System. Data. Sql. Server. Ce. dll ADO. NET providerSystem. Data. Sql. Server. Ce. Entity. dll ADO. NET Entity Framework Workaround. Issue Visual Studio IntelliSense and project templates available only in ASP. NET MVC version 3. Installing ASP. NET Web Pages does not also install tools for Visual. To resolve this issue, create a separate active system partition that can be used by BitLocker. The steps in this process vary, depending on the operating. Uninstall SQL Server Compact 4. Download and install the full version of. NET Framework 3. 5 SP1 from the following location Microsoft. NET Framework 3. 5 Service pack 1 Full PackageThen reinstall SQL Server Compact 4. Issue Cannot uninstall SQL Server Compact using the command line. Uninstallation of SQL Server Compact using command line options does not work in this release. Workaround. Use Programs and Features in the Windows Control Panel to uninstall Microsoft SQL Server Compact 4. ASP. NET Web Pages. This section of the document describes new features, changes, and known issues with the 1. ASP. NET Web Pages with Razor syntax. New Features. New Configuration setting added to disable the package manager. A new asp Admin. Manager. Enabled key is available for the lt app. Settings element in the web. The default value for this element is true, meaning that if it is not included in the web. To disable the package manager, add the following element to the web. Settings. lt add keyasp Admin. Manager. Enabled valuefalse. Settings. lt configuration. Changes. Change web. Pages Admin. Folder. Virtual. Path key renamed to asp Admin. Folder. Virtual. PathThe web. Pages Admin. Folder. Virtual. Path key that can be added to the web. Pages namespace. If you have used this element, you must rename it in the configuration file. Known Issues. Issue Passwords for membership users no longer recognized. The algorithm for creating and storing membership login passwords has been changed to be more secure. As a result, the passwords stored for members users created in Beta versions of ASP. NET Razor will not be recognized. Workaround If the site has not yet been put into production, remove the user records from the membership database. If database is live, programmatically regenerate existing passwords in the membership database. Issue Unexpected behavior when using a custom user table for membership. To initialize the membership provider for an ASP. NET Razor website, you call the Web. Security. Initialize. Database. Connection method. In Web. Matrix, the Starter Site template includes a call to this method in the App. Start. cshtml file. If the auto. Create. Tables parameter of this method is set to true by default, it is set to true in the Starter Site template, and if an unrecognized table name is passed to the method the second parameter, the method does not throw an error. Instead, it automatically creates the table. This can be a problem if you intend to use a custom user table for membership but pass the wrong table name to the Web. Security. Initialize. Database. Connection method. Because the method does not by default raise an error if the table you specify does not exist, and because it instead creates a new table, the application can appear to be working. However, application code that relies on your custom user table and on fields in it can eventually fail with unexpected errors. Workaround. Make sure that the name passed in the Initialize. Database. Connection method matches the user profile table in the membership database, or make sure that the auto. Create. Tables parameter is set to false. Issue Error message The Admin Module requires access to AppDataUnder some circumstances, trying to create users or otherwise work with the ASP. NET membership system can cause the page to display the error The Admin Module requires access to AppData. This occurs if the account that IIS or IIS Express is running under does not have permissions to create and write to the AppData folder under the website root. Workaround Manually create an AppData folder for the website. Then make sure that the Windows account that the application runs under typically NETWORK SERVICE has readwrite permissions for root folders of the application and for subfolders such as AppData. More detailed information is available in the Knowledge. Base article Problems with SQL Server Express user instancing and ASP. Web Application Projects. Issue Failed to generate a user instance of SQL Server error. If a Web. Matrix Web application uses SQL Server Express and is running IIS 7. Windows 7 or Windows Server 2. R2, you might see an error that indicates that SQL Server cannot retrieve the users local application path at run time. Workaround Make sure that the Windows account that the application runs under typically NETWORK SERVICE has readwrite permissions for root folders of the application and for subfolders such as AppData. More detailed information is available in the Knowledge. Base article Problems with SQL Server Express user instancing and ASP. Web Application Projects. Issue Files that contains package manager resources or package manager passwords are servable under IIS 6. If you deploy an ASP. NET Web Pages Razor application that was built using the RC2 release, and if the application contains a password. AppDataadmin, IIS 6. Workaround Rename the password. By default, IIS 6. In IIS 7, no files in the AppData folder are served, so you do not need to rename the files. Issue Uninstalling packages installed using the Beta 3 release does not completely remove package components.