1.1 Supported Architectures:
1.2 Supported Operating Systems
2. Known Issues
If you have installed an earlier version of Visual Studio, such as a Visual Studio Code Name "Orcas" Community Technical Preview (CTP), then you must uninstall it in the following order:
1. Go to the Control Panel and open Add or Remove Programs.
2. Remove "Microsoft SQL Server Compact Edition 3.5".
3. Remove "Microsoft SQL Server Compact Edition 3.5 Design Tools".
4. Remove "Microsoft SQL Server Compact Edition 3.5 for Devices".
5. Remove "Microsoft Visual Studio Performance Collection Tools".
6. Remove "Windows Mobile 5.0 SDK R2 for Pocket PC".
7. Remove "Windows Mobile 5.0 SDK R2 for Smartphone".
8. Remove "Crystal Reports 2007".
9. Remove "Visual Studio Asset System".
10.Remove "Visual Web Developer Design Service Reminder Tools".
11.Remove "Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System Runtime".
12.Remove "Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System Runtime Language Pack". This step is not required if you have only the English edition. 13.Remove "Microsoft Visual Studio Tools for Office Runtime 3.0".
14.Remove "Microsoft Visual Studio Codename Orcas Professional" or other related Visual Studio IDE installations, such as Professional, Standard, Enterprise Architect, or Team Suite.
15.Remove "Microsoft Document Explorer".
16.Remove "Microsoft Document Explorer 2005 Language Pack". This step is not required if you have only the English edition.
17.Remove "Microsoft Device Emulator 3.0".
18.Remove "Microsoft .NET Compact Framework 2.0 SP1".
19.Remove ".NET Framework 2.0 SDK".
20.Remove "Microsoft Visual Studio Codename Orcas Remote Debugger".
21.Remove "Microsoft Visual Studio 64bit Prerequisites Beta". This step is required only if Visual Studio is installed on a 64-bit computer.
22.Remove "Microsoft .NET Framework 3.5".
If you uninstall Visual Studio 2008 by using Add or Remove Programs, all pre-release components will be chain-uninstalled with the product. This lets the user uninstall an earlier release, and then install a newer release without manually uninstalling the product.
Note: If two or more Visual Studio 2008 products are installed on the same computer and then one of them is uninstalled, the remaining products may break. The chained uninstallation of any pre-release version will chain-uninstall applications that are shared across the products. To fix any remaining product, run repair on it so that the shared applications will be reinstalled.
To resolve this issue:
No workaround is available.
During Visual Studio Setup on Vista there is a required reboot to apply an update to the OS. If the user is not logged in using the Administrator account, Visual Studio Setup will not resume automatically after the machine is restarted.
To resolve this issue:
After the machine restarts, log in and re-launch setup manually to resume Visual Studio Setup or run setup while logged in using the Administrator account.
This issue can be safely ignored, and Setup will resume shortly.
To resolve this issue:
No workaround is available.
Installing Visual Studio 2008 may bring up a message that prompts you to close running applications. Some of the applications may have numeric identifiers and some may have an empty identifier.
In the message, you may see the Process IDs of applications that should be closed. Names of applications are not shown.
To resolve this issue:
We recommend that you close these applications so that they do not affect the installation process.
You can find names of applications that should be closed by looking up the Process IDs in Task Manager.
1. Press CTRL+ALT+DEL and then click Task Manager.
2. On the View menu, click Select Columns.
3. Select PID (Process Identifier) and then click OK.
4. In Task Manager, click PID to sort entries by PID.
5. Look for the Process IDs that are shown in the message.
You may also click Ignore in the message box and then continue with the installation. This may require a reboot at the end of setup.
Installing Visual Studio 2008 requires a reboot on all Windows Vista platforms. When the user is prompted, there may be 2 reboot dialog boxes. One is from the Visual Studio 2008 Setup and one is from the Windows Vista operating system. It is recommended that the user only use the Visual Studio 2008 Setup prompt.
To resolve this issue:
No workaround is available.
When Orcas is installed on a Windows Vista SP1 Beta platform, the .Net Framework has mismatched versions. This causes random failures in the product.
To resolve this issue:
No workaround is available.
When Visual Studio 2008 is installed on the same computer as Visual Studio 2005 this causes Visual Studio 2005 repair to fail to repair the .NET Framework 2.0.
To resolve this issue:
Repair the .NET Framework 2.0 separately from Add or Remove Programs.
When installing Visual Studio 2008 on a Windows Vista computer that has had earlier versions of Visual Studio, Setup fails during the installation of the .NET Framework 3.5 component.
To resolve this issue:
Open the Control Panel, select Programs & Features, click on the "View installed updates" located on the Tasks pane. Select and uninstall the following Windows updates:
- Hotfix for Microsoft Windows (KB110806)
- Hotfix for Microsoft Windows (KB930264)
- Hotfix for Microsoft Windows (KB929300)
Installing Visual Studio 2008 on Windows Vista could sometimes give a error. This could happen if SMS or Windows Update are installing packages on the computer at the same time as Visual Studio 2008 Setup.
To resolve this issue:
Wait for SMS/Windows Update to finish. Re-boot the machine and then restart VS Orcas setup.
Setup finish pages has script error 887600de in SIT13948.tmp\install1.htm
Line: 159
Character: 5
Error: Could not complete operation due to error 887600de.
Code: 0
URL: file:///D:\Users\MSLAB2\AppData\Local\Temp\SIT13948.tmp\install1.htm
To resolve this issue:
Clicking Yes to both instances of the error dialog allows Setup to finish.
The user gets the message "A problem has been encountered while loading the setup components. Canceling setup" and Setup gets cancelled. This only occurs on systems that do not have Windows Installer 3.1 installed. Users should install Windows Installer 3.1 and then retry Setup.
To resolve this issue:
1. In Add or Remove programs and check if Windows Installer 3.1 is in the list of installed programs.
2. If Windows Installer 3.1 is not in installed programs list, please use following steps.
a. Go to Windows Installer 3.1 Redistributable (v2) and install Windows Installer 3.1
b. Retry Visual Studio 2008 installation
Setup will fail if the network share path from where Visual Studio 2008 is installed is too long.
To resolve this issue:
Use a network share location that is less than 65 characters.
If you install Visual Studio 2008 Express Edition and select only Visual Basic or Visual C#, and do not select the VWD (Visual Web Developer) option, the WCF web application templates are installed but not usable. In this case, the WCF templates should not have been installed.
To resolve this issue:
Install Visual Studio 2008 with the Visual Basic, C#, and VWD options.
Setup stops with an error dialog box: "Setup failed to stop Windows Installer service. You must stop all other applications running Windows Installer service or restart your computer before the installation"
To resolve this issue:
Please try following options.
- This error message indicates that another setup than Visual Studio 2008 might already be running on your computer. After other setup has completed, please restart your computer and run Visual Studio 2008 Setup.
- This might also result due to windows updates being currently installed on the computer. Please wait for windows updates to install. Please restart your computer and run Visual Studio 2008 Setup.
- Check for msiexec.exe in the task manager. If msiexec.exe is already running, please wait for it to finish. Please restart your computer and run Visual Studio 2008 Setup.
- If none of the above apply to your problem, please re-start your computer and run Visual Studio 2008 Setup.
2.1.15 Visual Studio SharePoint Workflow features have specific installation requirements
To use the SharePoint workflow tools in this release, you must install the following products and components in the specific order listed.
To resolve this issue:
Install the following products in the listed order.
1) Windows 2003 Server
2) Internet Information Services (IIS) (Through control panel -> A&R windows components -> Application Server -> Details -> Internet Information Services (IIS))
3) Install .NET Framework 2.0 & 3.0
4) Enable ASP.NET 2.0.5727 in IIS Manager
5) Install Microsoft Office SharePoint Server 2007. Make sure to run the configuration wizard
6) Install Visual Studio 2008 Beta 2. Use default install or make sure the Tools for Office are selected in the Custom install page of the Setup wizard
7) Optional: SMTP Service. Installing this service allows you to use SharePoint email-enabled features. Consult SharePoint product documentation to learn more about these capabilities.
2.1.16 Javascript intellisense, coloring and syntax validation may not work when Silverlight Tools or Team Explorer (Team Foundation Client) Beta 2 is installed
Uninstalling Silverlight Tools for Visual Studio 2008 Beta 1 or installing Team Explorer (Team Foundation Client) Beta 2 after installing Visual Web Developer 2008 Express Edition Beta 2 may lead to non availability of Javascript intellisense, coloring and syntax validation. This is due to a setup conflict for the Javascript authoring component.
To resolve this issue:
Repair the Visual Web Developer 2008 Express Edition Beta 2 installation by running the setup again. This will restore the Javascript functionality in Visual Web Developer 2008 Express Edition Beta 2.
If you install Visual Studio2008 on the same computer as Visual Studio 2005 and then uninstall Visual Studio 2008, some Visual Studio 2005 features might stop working.
To resolve this issue:
Use Add or Remove Programs to repair Visual Studio 2005.
Uninstalling any Visual Studio 2008 product triggers .NET 3.5 Framework to be uninstalled. This breaks any other installed Visual Studio 2008 product because all Visual Studio 2008 products depend on the .NET 3.5 Framework.
To resolve this issue:
Repair the installation by using Add or Remove Programs, or by downloading and running the Visual Studio 2008 product installer.
On computers with Visual Studio 2005 or Visual Studio 2005 SP1, Platform Builder 6.0, and Visual Studio 2008 installed, uninstalling Visual Studio 2008 will stop Smart Device development on Visual Studio 2005 or Visual Studio 2005 SP1 from working.
To resolve this issue:
After uninstalling Visual Studio 2008, launch Device Emulator Manager from the command line before launching Visual Studio 2005, Visual Studio 2005 SP1 or Platform Builder 6.0
SQL Server Compact 3.5 .msi files are not removed when you uninstall Visual Studio Code Name “Orcas” CTP. If SQL Server Compact 3.5 .msi files are not manually removed after uninstalling Visual Studio Code Name “Orcas” CTP, the latest version of the SQL Server Compact 3.5 .msi files will not be installed with the newer versions of Visual Studio.
To resolve this issue:
1. To manually remove SQL Server Compact 3.5 components, go to Add or Remove Programs on the Control Panel. The SQL Server Compact 3.5 components are:
SQL Server Compact 3.5
SQL Server Compact 3.5 for Devices
SQL Server Compact 3.5 Design Tools
2. Run Orcas setup and install the SQL Server Compact components.
If a user installs any of the following Visual Studio 2008 Beta 2 products (VSTS, Visual Studio 2008 Beta 2 Professional Edition, Visual Studio 2008 Beta 2 Standard Edition, Visual C++ 2008 Beta 2 Express Edition) and then installs another product of (VSTS, Visual Studio 2008 Beta 2 Professional Edition, Visual Studio 2008 Beta 2 Standard Edition, Visual C++ 2008 Beta 2 Express Edition), uninstalling the first will result in the remaining product having missing Compile and will not be able to compile some projects.
To resolve this issue:
This can be fixed by repairing (in Add or Remove Programs) any install of Beta 2 that exhibits this behavior.
Installing Visual Studio 2008 may bring up a message that prompt to close running applications. Some of the applications may have numeric identifiers and some may have an empty identifier. In the message, you may see the Process IDs of applications that should be closed. Names of applications are not shown.
To resolve this issue:
We recommend that you close these applications so that they do not affect the installation process. You can find names of applications that should be closed by looking up the Process IDs in Task Manager.
1. Press CTRL+ALT+DEL and then click Task Manager.
2. On the View menu, click Select Columns.
3. Select PID (Process Identifier) and then click OK.
4. In Task Manager, click PID so that the entries are sorted by PID and then find the application names.
You may also click Ignore in the message box and continue. Doing this may require a reboot at the end of uninstallation.
If Visual Studio 2008 Beta 2 is uninstalled, all SQL Server Compact 3.5 components are uninstalled. This can create problems if two Visual Studio 2008 Beta 2 products (for example, Visual Studio 2008 Beta 2 Standard Edition and Visual Studio 2008 Beta 2 C# Express Edition) are installed on the same computer . If one of the Visual Studio 2008 Beta 2 products is uninstalled, it will uninstall all the SQL Server Compact 3.5 components, and the other Visual Studio 2008 Beta 2 product will not function correctly.
To resolve this issue:
Run the Visual Studio 2008 Beta 2 product installation and choose Repair to reinstall the SQL Server Compact 3.5 components.
If you specify the following Transact-SQL (T-SQL) statements at the end of a table definition in a SQL Server 2000 database project, no error is reported even though the option is not supported. The vardecimal storage format requires SQL Server 2005 SP2 or newer.
GO
exec sp_tableoption 'Table1', 'vardecimal storage format', 1
To resolve this issue:
Remove the unsupported statements from the table definition or change the project version to SQL Server 2005 in the project settings. You must have an instance of SQL Server 2005 SP2 or newer as your design-time database and target database.
When "devenv /resetuserdata" is run from a command prompt, on any operating system, it fails to reset all the appropriate user settings.
To resolve this issue:
On Windows Vista:
1. Remove folder %APPDATA%\Microsoft\VisualStudio\9.0
2. Remove folder %LOCALAPPDATA%\Microsoft\VisualStudio\9.0
3. Delete registry hive HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0
4. Run devenv /resetuserdata to create all the relevant directories and put Visual Studio 2008 back in its first launch state.
On other operating systems:
1. Remove folder %USERPROFILE%\Application Data\Microsoft\VisualStudio\9.0
2. Remove folder %USERPROFILE%\Local Settings\Application Data\Microsoft\VisualStudio\9.0
3. Delete registry hive HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0
4. Run devenv /resetuserdata to create all the relevant directories and put Visual Studio 2008 back in its first launch state.
If a user installs Visual Studio 2008 on a computer that has Windows Mobile 6 SDK installed, then Visual Studio 2008 will fail to recognize the SDK. Repairing Windows Mobile 6 SDK will not solve this.
To resolve this issue:
1) Uninstall Windows Mobile 6 SDK.
2) Install Visual Studio 2008.
3) Install Windows Mobile 6 SDK.
If a user opens an existing Smart Device project that has a reference to SQL Server Mobile 3.0 or SQL Server Compact v3.1, the format of the SDK file will not be automatically upgraded to SQL Server Compact 3.5. The user must manually upgrade the SDF file format before running the application.
To resolve this issue:
1. In Solution Explorer, double-click the SDK file to start the upgrade wizard.
2. Follow the instructions.
Some changes on the diagram may lead to an exception and the message "Exception has been thrown by the target of an invocation" or "Failed to create class 'xxxxxxx'".
Here are some examples of operations that might fail:
- Create a new type from the Toolbox.
- Select and delete an inheritance line.
- Undo that follows a paste operation.
To resolve this issue:
Edit the code in the code editor. Here are the steps to follow:
1. Close the class diagram window.
2. Make the desired change in the code editor (for example, add a new module).
3. Re-open the class diagram.
4. If a new type was added, you can add it to the diagram by dragging it from the class view window to the diagram surface.
If the queries in a transaction scope take too long to finish and the transaction scope times out, the data is partially committed to the database. Any data committed to the database before the transaction scope timeout will be rolled back, and the data committed to the database after the transaction scope timeout will be committed to the database.
To resolve this issue:
To avoid such a situation, increase the time-out value.
SQL Server Compact 3.5 database files can be only encrypted while the database file is being created or while a SQL Server 2005 Compact Edition or SQL Server 2005 Mobile Edition database (.sdf) file is being upgraded to SQL Server Compact 3.5. After a SQL Server Compact 3.5 database file has been created or upgraded from earlier version, the encryption mode (Platform Default, Engine Default, PPC2003 Compatibility) cannot be changed, and an unencrypted database file cannot be encrypted. The Encryption Mode token in SqlCeConnectionString will be ignored while an existing SQL Server Compact 3.5 database is being opened. The Encrypt token is not used in SqlCeConnectionString. The token is retained in SQL Server Compact 3.5 for backward compatibility. The token should not be used and it will be deprecated in future.
To resolve this issue:
To change the encryption mode of an existing SQL Server Compact 3.5 database or to encrypt an existing unencrypted SQL Server Compact 3.5 database, create a new SQL Server Compact 3.5 database and then copy the schema and data to the new database.
Upgrading a project that was created in Visual Studio 2005 to Visual Studio 2008 does not upgrade SQL Server Compact 3.5 references or database file.
To resolve this issue:
After you upgrade a Visual Studio 2005 project to Visual Studio 2008, manually update the references to SQL Server Compact 3.5 and upgrade the database file to SQL Server Compact 3.5.
To upgrade the references in Visual Studio 2008, on the View menu, click on Solution Explorer, and then expand References. Select a reference and then right-click it and click Properties.
To upgrade the database file, use the Upgrade to SQL Server Compact 3.5 dialog box in Visual Studio 2008. To access the Upgrade to SQL Server Compact 3.5 dialog box, click Data, click Add New Data Source and then click Add Connection. If an earlier version of the database file is opened an error message pops up. If you click OK, the Upgrade to SQL Server Compact 3.5 dialog box appears.
Test Client is a new application in Visual Studio 2008. Here is a list of features that are currently unsupported:
- Duplex Contract
- Message Contract and XML Serialization, ASP.NET Web Service
- Session Controlling
- ContextBinding
- Transaction
- Windows Card Space, Certificate, User name/Password, Windows Authentication
- Types: Stream, IDictionary Collection, dataset
To resolve this issue:
Do not use currently unsupported features in Test Client. Doing so may cause instability.
Some IntelliSense type or member descriptive text is missing for the following assemblies:
- Microsoft.Build.Tasks.dll
- Microsoft.Build.Utilities.dll
- System.Data.Linq.dll
- System.Data.DataSetExtensions.dll
- System.Windows.Presentation.dll
- Microsoft.ManagementConsole.dll
- Microsoft.Ink.JournalReader.dll
- Microsoft.windowsmediaservices.dll
- System.ServiceModel.Install.dll
- PresentationUI.dll
- System.Net.dll
- System.DirectoryServices.AccountManagement.dll
- Microsoft.VisualC.STLCLR.dll
To resolve this issue:
The signature for these types and members is still available and descriptive text is available in the MSDN API reference documentation.
To open a solution that is stored in Visual SourceSafe source control for the first time, the user typically clicks Open Project/Solution on the File menu, and then clicks the Visual SourceSafe icon. When Visual Studio 2008 is used with Visual SourceSafe 2005, this icon will not work or may be missing entirely.
To resolve this issue:
The quickest workaround is to avoid using the Open From SourceSafe feature. If the user has previously used the solution, he should open it from disk (steps 5-6 below). If not, he can retrieve the solution by using Visual SourceSafe Explorer and then open it from disk:
1) Open Visual SourceSafe Explorer.
2) Navigate to the folder that contains the solution and all project files.
3) Right-click the solution and then perform a Get by using the "recursive" option.
4) Choose a local working folder if prompted to do so.
5) Start Visual Studio 2008.
6) On the File menu,click Open Project/Solution, and then browse to the location where you downloaded the files from SourceSafe.
The more permanent workaround is to install the SourceSafe 2005 GDR which is currently under development. Releases will be announced at
http://msdn2.microsoft.com/en-us/vstudio/aa718670.aspx
Visual Studio 2008 throws an exception when trying to debug applications on AMD64 computers with the Japanese version of Visual Studio 2008 installed. The debug session is canceled. This effectively makes it impossible to run an application under the debugger on JPN AMD64.
To resolve this issue:
Open the properties of the project
Select "Build"
Change the "Platform Target" to X86
Debugging should work as expected.
There are no known issues.
You receive multiple build errors and warnings when you try to add a Windows Forms Application project to a Website or WCF Service Application.
To resolve this issue:
On the Build menu, click Rebuild or click Clean.
Extension methods are not shown in the context menus of the objects that are created in Object Test Bench (OTB) window. Therefore, users cannot invoke extension methods from the OTB window.
Extension methods is a new language feature introduced in C# 3.0, Visual Basic 9.0.
To resolve this issue:
No workaround is available.
Any use of the the 'checked' or 'unchecked' expressions in C# in the debugger windows (such as the immediate window or watch window) will cause Visual Studio 2008 to crash.
To resolve this issue:
Avoid using these expressions in the debugger. You can write the expression in your source code and inspect the result of the expression in the debugger without experiencing this crash.
2.3.3.4 Visual Studio crashes when C# IDE features are invoked on explicit interface members defined in referenced project
Visual Studio will crash when invoking C# IDE features such as IntelliSense or Quick Info tooltips on explicit interface members defined in a referenced project. A simple example is as follows:
1. Create a new Project named ProjectA
2. Inside ProjectA, add a new file with the following content:
public interface Interface {
void Method();
}
public class ImplClass : Interface {
void Interface.Method() { }
}
3. Create a second Project called ProjectB, that references ProjectA
4. Add a file with the following content:
class Program {
static void Repro() {
new ImplClass().Method();
}
}
5. Visual Studio will crash when you hover over the "Method" token in the file you just created.
To resolve this issue:
No workaround is available.
The O/R Designer in Visual Studio 2008 maps database columns of Binary, Image, Timestamp and Varbinary types to System.Byte[] when a table that contains columns of these types are dragged to the designer. Because System.Byte[] is not supported for identity members, setting these columns as a primary key will result in a runtime error. Note that SqlMetal.exe in Visual Studio 2008 maps columns of the above listed types to System.Data.Linq.Binary type, which can be used as primary key. Opening a SqlMetal.exe-generated .dbml file in the O/R Designer might corrupt the mapping for these types.
To resolve this issue:
If you must use tables with Binary, Image, Timestamp or Varbinary columns as the primary key, use SqlMetal.exe to create the .dbml file and generate the LINQ to SQL code.
If you add a previously created .dbml file to a project by using the "Add Existing Item" dialog box, and the connection string that is referenced in the .dbml file is not found in the Application Settings of the project, a warning is displayed and asks whether the connection string should be added to the Application Settings automatically. Answering "Yes" to this warning will update the .dbml file and the Application Settings accordingly. However, doing this leaves the generated code in an incomplete state with the DataContext default constructor missing, and code will not be regenerated until a Save or Save All command is issued.
To resolve this issue:
After you choose "Yes" in the warning, click either Save or Save All to initiate code generation.
2.3.4.3 LINQ features in .NET Framework 3.5 Beta 2 cannot be used by default in medium or partial trust configurations
By default, the LINQ features in .NET Framework 3.5 Beta 2 cannot be used in medium trust or partial trust configurations. Enabling LINQ in these configurations requires a machine-level change to .NET Framework configuration.
In medium trust or partial trust configurations, the code permissions granted to an ASP.NET website are determined by a Code Access Security (CAS) policy file on the Web server. When .NET Framework 3.5 is installed on a Web server, websites continue to use the same CAS policy file as .NET Framework 2.0.
The LINQ feature set in .NET Framework 3.5 requires the CAS policy file to grant a new permission, called RestrictedMemberAccess, which is not granted by default on ASP.NET 2.0. To enable LINQ to work in medium or partial trust, you need to modify the CAS policy file to grant this additional policy.
NOTE: Making this change will also grant this policy to ASP.NET 2.0 websites running on the same server. We have determined this to be an acceptable change for hosted sites that run under medium trust. This change will have no impact on existing ASP.NET 2.0 websites that can run under medium or partial trust.
To resolve this issue:
To enable LINQ for medium trust, please follow the steps below on the server:
1. Open a command prompt, and go to the directory that contains your ASP.NET 2.0 trust policy files. This can be found under the Windows directory, at
%windir%\Microsoft.NET\Framework\v2.0.50727\config
2. Determine which CAS policy file to modify. If you are using medium trust, this file will be web_mediumtrust.config.
3. Make a backup of the existing file.
4. Examine the <SecurityClasses> section of your CAS policy file. If the section does not contain an entry named ReflectionPermission, add a new entry as follows:
<SecurityClass Name="ReflectionPermission" Description="System.Security.Permissions.ReflectionPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
If you are using the default medium trust settings, you will need to add this entry. Depending upon your trust setting, your CAS policy file may already contain this entry.
5. Examine the <NamedPermissionSets> section of your CAS policy file. If the section does not contain an entry named ReflectionPermission, add a new entry as follows:
<IPermission
class="ReflectionPermission"
version="1"
Flags="RestrictedMemberAccess"
/>
If you are using the default medium trust settings, you will need to add this entry.
If you are using another trust configuration, and the section already contains an entry named ReflectionPermission, you can modify the Flags setting to add RestrictedMemberAccess permission. Flags should be separated by a comma. For example, if you are using the default high trust settings, you can modify this section as follows:
<IPermission
class="ReflectionPermission"
version="1"
Flags="ReflectionEmit, RestrictedMemberAccess"
/>
6. Save the file, and restart the Web server.
2.3.4.4 Using LINQ in VB in an ASP.NET Website under Partial Trust
To enable support for new compiler features in .NET Framework 3.5, Visual Studio
2008 Beta 2 inserts a new
<system.codedom>
<compilers>
<compiler language="c#;cs;csharp" extension=".cs"
compilerOptions="/warnaserror-" warningLevel="4"
type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
<providerOption name="CompilerVersion" value="v3.5"/>
</compiler>
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" compilerOptions="/optioninfer+" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
<providerOption name="CompilerVersion" value="v3.5"/>
</compiler>
</compilers>
</system.codedom>
When you run the application in medium trust or another partial trust setting, ASP.NET will raise an error noting that “the current trust level does not allow the use of the ‘compilerOptions’ attribute”. NOTE: Depending on the security settings of your server, this error message may or may not be visible to you.
To resolve this issue:
To avoid this problem,
you can remove the compilerOptions setting, as well as the warningLevel setting,
from this configuration section in your application’s web.config file after you
have created or migrated your application. After making the change, your
<system.codedom>
<compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
<providerOption name="CompilerVersion" value="v3.5"/>
</compiler>
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
<providerOption name="CompilerVersion" value="v3.5"/>
</compiler>
</compilers>
</system.codedom>
The workaround above also has the following impact on your ASP.NET Web applications:
1. For websites built with Visual Basic, the workaround prevents using the new LINQ capabilities of .NET Framework 3.5 on an ASP.NET page. To fix this, users can add the following line to the beginning of their Visual Basic codebehind file, and any other Visual Basic code files that use LINQ:
Option Infer On
Inline Visual Basic inside the .aspx or .ascx page (within a <script runat=”server”> tag) will not be able to use LINQ with this workaround. Users should move this code to a codebehind file. Other ASP.NET page features that use LINQ, such as the LinqDataSource control, will continue to work normally.
2. For websites built with C#, compiler warnings will no longer show up in the Visual Studio errors pane on compilation.
If the Icons property of a form region contains icons and an Active X control on the form region contains icons, you will receive the following error when you compile the project:
"The name 'resources' does not exist in the current context"
This error occurs because the InitializeManifest method of the form region designer code file is missing a variable named 'resources' of type System.ComponentModel.ComponentResourceManager.
To resolve this issue:
Set the Localizable property of the form region to True. This adds the 'resources' variable to the InitializeManifest method of the form region designer code file.The project should successfully compile.
If you set the platform target to x64 in the project properties on the Build tab, you can compile the project but the solution will not run. Setting the platform target to x64 requires the solution to run in a 64-bit process. Office runs in a 32-bit process.
To resolve this issue:
Set the platform target in the Build tab of the project properties to 'Any CPU'. This will cause the solution to run in Office as a 32-bit process.
You cannot create Microsoft Office InfoPath 2007 projects if Visual Studio Tools for Applications under .NET programmability support is not installed before you install Visual Studio 2008 Beta 2.
To resolve this issue:
Before you install Microsoft Visual Studio 2008 Beta 2, install Visual Studio Tools for Applications from Microsoft Office or InfoPath Setup, as follows:
1. Open Add or Remove Programs in Windows XP or Windows 2003, or Programs and Features in Windows Vista.
2. Select the Microsoft Office Enterprise 2007 or Microsoft Office InfoPath 2007 item, and then click Change.
3. Choose Add or Remove Features, and then click Continue.
4. Expand the Microsoft Office InfoPath node and ensure that all items under .NET Programmability Support are selected, including Visual Studio Tools for Applications.
5. Click Continue and wait for installation to complete.
6. Install Microsoft Visual Studio 2008 Beta 2.
If you have already installed Microsoft Visual Studio 2008 Beta 2, you must reinstall Visual Studio Tools for Office, as folows:
1. Open Add/Remove Programs in Windows XP or Windows 2003, or Programs and Features in Windows Vista.
2. Select Microsoft Visual Studio 2008 and then click Change or Remove.
3. Choose Add or Remove Features on the Visual Studio maintenance page.
4. Under Visual Basic and Visual C#, clear the Visual Studio Tools for Office option, and then click Update.
5. After maintenance is complete, run Change or Remove again. This time, under Visual Basic and Visual C#, select the Visual Studio Tools for Office option, and then click Update. This installs Visual Studio Tools for Office and the Microsoft Office InfoPath 2007 templates.
Previewing Microsoft Office InfoPath 2007 form templates by pressing F5 or by clicking Preview will fail with an error in Visual Studio 2008, unless InfoPath 2007 Service Pack 1 or the QFE is installed.
To resolve this issue:
The QFE is available on the Microsoft Visual Studio 2008 Beta 2 download site at http://go.microsoft.com/fwlink/?LinkId=95488.
The Microsoft Office InfoPath 2007 embedded design experience is available only in English for Microsoft Visual Studio 2008 Beta 2. When you use Microsoft Visual Studio 2008 Tools for Office Beta 2 to create or modify an InfoPath 2007 form template, menus and some code comments will appear in English for all installed locales.
To resolve this issue:
To use the English version of the Microsoft Office InfoPath 2007 project files in a localized version of Microsoft Visual Studio 2008 Tools for Office Beta 2, the following additional steps are required:
1. Close Visual Studio 2008.
2. Locate the file VSTO90InfoPathFormTemplate.zip,
which is typically located in one of the following: For C#:
3. Copy this file to one of the following
folders, as appropriate, where LCID is the locale ID of your localized installation (for example, 1041 for Japanese). For C#:
4. Open the Visual Studio Command Prompt and run the following command: Devenv.exe /setup
5. Restart Visual Studio.
If you save a Word document project before you build the project, Visual Studio 2008 crashes. This only happens if the Visual Studio 2008 profile is set to Visual Basic Developer.
To resolve this issue:
Build Word document projects before you save them.
Many of the limitations that Microsoft Office Word imposes on content controls at run time are not enforced in document-level projects for Word at design time. When you design the UI of your solution in Visual Studio 2008, be sure to modify content controls only in ways that are supported at run time. Specifically, do not insert any non-text content, such as other content controls, pictures or tables, into a plain text content control. Although Word appears to let you insert this kind of content at design time, this content may cause document corruption when the document is re-opened. Similarly, do not insert any content other than pictures into a picture content control. If you are unsure whether a content control accepts a certain type of content or not, then first run the solution without that content and then try to add it to the content control at run time. If Word does not let you to do that, then you should not insert that kind of content into that content control at design time.
If you modify a content control at design time in a way that the control does not support at run time, the Visual Studio 2008 designer will not alert you of the unsupported changes. However, when you debug or run the project, or if you save and then reopen the project, Word will display an error message and request permission to repair the document. When you repair the document, Word removes all unsupported content and formatting from the control.
To resolve this issue:
Do not add unsupported content to content controls at design time.
You can configure how Visual Studio 2008 handles the file locations for newly created projects by selecting or clearing the "Save new projects when created" checkbox on the Projects and Solutions page of the Options dialog box. When the "Save new projects when created" checkbox is selected, you can specify a location for your project in the New Project dialog box. When cleared, new projects are created as temporary projects, and you will not be prompted for a permanent location until you save the project and its items.
The problem occurs when the checkbox is cleared and you create a new document-level solution such as a Word Document project. After you add content such as text or a control to the document surface of the visual designer, you click Save All on the File menu and then click Save in the Save Project dialog box. These conditions will cause Visual Studio 2008 to fail or enter an uncertain state.
To resolve this issue:
Select "Save new projects when created" on the Project and Solutions page of the Options dialog box.
The SharePoint tab will not appear in the Toolbox unless the Microsoft Office SharePoint Server 2007 installation is performed in a specific order.
To resolve this issue:
Add a custom Toolbox tab that contains
the Microsoft Office SharePoint Server 2007 workflow controls.
Directions:
1) Right-click the Toolbox and then click Add Tab.
2) A new blank tab is added to the Toolbox.
3) In the text box at the top of the new tab, type a name for the tab and then press
ENTER.
4) The new tab appears at the bottom of the Toolbox.
5) On the Tools menu, click Choose Toolbox Items, or
right-click the Toolbox and then click Choose Items.
6) To sort the items that are displayed on a tab of the Choose Toolbox Items dialog
box, click the Namespace column header.
7) Scroll down until you find the controls in the Microsoft.SharePoint.WorkflowActions
namespace.
8) Select these controls, and then press OK to close the Choose Items dialog box.
9) The newly added items will appear on the recently created Toolbox tab.
This issue occurs when you create a Web site by using Visual Studio 2008 and choose either the HTTP or FTP hosting option instead of the default File System option. If you then add an AJAX-enabled WCF Service to the site by using the "Add New Item" command, the service is added but may not work as expected.
To resolve this issue:
You can use one of the following workarounds to resolve the issue:
- Use the ASP.NET Web Application project type instead of a Web site solution.
- Use the File System hosting option instead of HTTP or FTP.
- If you must use a Web site with HTTP or FTP, add the AJAX-enabled WCF service and then modify the resulting web.config file as follows. The <system.servicemodel> element contains a <services> element. You must remove the namespace information from each <service> element and <endpoint> element.
For example:
Original generated configuration
<services>
<service name="Namespace.ServiceName">
<endpoint address="" behaviorConfiguration="Namespace.ServiceAspNetAjaxBehavior"
binding="webHttpBinding" contract="Namespace.ServiceName"/>
</service>
</services>
Fixed configuration
<services>
<service name="ServiceName">
<endpoint address="" behaviorConfiguration="Namespace.ServiceAspNetAjaxBehavior"
binding="webHttpBinding" contract="ServiceName" />
</service>
</services>
When a Web project is started on Windows Vista, it may fail with the following error:
"Unable to start debugging on the web server. Strong name validation failed.
Click Help for more information."
To resolve this issue:
This issue may be worked around by disabling strong name validation for a Visual Studio file (iisresolver.dll). To do this, use the following steps:
1. Click Start, All Programs, Accessories, Command Prompt, and then select the 'Run as administrator' option.
2. You may see the screen grey out and a 'User Account Control' dialog box come up. If so, click 'Continue' so that the command prompt starts.
3. Run the following command:
32-bit computer: "%ProgramFiles%\Microsoft SDKs\Windows\v6.0A\bin\sn.exe" -Vr "%ProgramFiles%\Microsoft Visual Studio 9.0\Common7\IDE\iisresolver.dll"
64-bit computer: "%ProgramFiles%\Microsoft SDKs\Windows\v6.0A\bin\x64\sn.exe" -Vr "%ProgramFiles(x86)%\Microsoft Visual Studio 9.0\Common7\IDE\iisresolver.dll"
This assumes that Visual Studio 2008 was installed to the default location. If Visual Studio 2008 was installed to another location, then '%ProgramFiles%\Microsoft Visual Studio 9.0' should be replaced with the path where Visual Studio 2008 was installed.
This also assumes that sn.exe is present on your computer. Sn.exe is typically installed as part of the Microsoft Windows SDK that is included in Visual Studio 2008. If sn.exe is missing from your computer, it can also be obtained with the .NET Framework 2.0 SDK. The x86 version of the SDK can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyID=FE6F2099-B7B4-4F47-A244-C96D69C35DEC. The x64 version of the SDK can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyId=1AEF6FCE-6E06-4B66-AFE4-9AAD3C835D3D.
2.3.6.3 VSTO customizations do not run on a computer without Visual Studio installed
You can use the Publish Wizard to create a Setup.exe file for a VSTO customization. You can install the published customization on another computer by running the generated Setup.exe file. This will install the .NET Framework version 3.5 and the VSTO 3.0 runtime as prerequisites, if required. In some circumstances, the VSTO 3.0 runtime is not installed correctly if a restart is required after installing the .NET Framework. If this happens, the customization will not run.
To resolve this issue:
Update the bootstrapper package for the .NET Framework to ensure that the computer is restarted before Setup.exe begins installing the VSTO 3.0 runtime.
1) Open the directory %programfiles%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFX35\
2) Locate the language folder for your language of Visual Studio. For example, the folder for Japanese versions of Visual Studio is 'ja'.
3) Open the package.xml file in a text editor or other editing application.
4) Locate the following XML fragment:
<Commands Reboot="Defer">
<Command PackageFile="dotNetFx35setup.exe"
Arguments=' /lang:enu /passive /norestart'
EstimatedInstalledBytes="30000000"
EstimatedTempBytes="30000000">
5) Change the value of the Reboot attribute from "Defer" to "Immediate".
The resulting element is this: <Commands Reboot="Immediate">
2.3.6.4 ASP.NET Web applications or sites built with Visual Studio 2008 Beta 2 and .NET Framework 3.5 Beta 2 cannot be run in medium or partial trust
When you use Visual Studio 2008 Beta 2 to build a new ASP.NET Web application or website with .NET Framework 3.5, or migrate an existing ASP.NET application or website to .NET Framework 3.5, the resulting application will not run in medium trust or any other partial trust configuration. This issue affects all versions of Visual Studio 2008 Beta 2. A workaround is available below.
To enable support for new compiler
features in .NET Framework 3.5, Visual Studio 2008 Beta 2 inserts a new
<system.codedom>
<compilers>
<compiler language="c#;cs;csharp" extension=".cs" compilerOptions="/warnaserror-" warningLevel="4" type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
<providerOption name="CompilerVersion" value="v3.5"/>
</compiler>
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" compilerOptions="/optioninfer+" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
<providerOption name="CompilerVersion" value="v3.5"/>
</compiler>
</compilers>
</system.codedom>
This configuration entry contains a setting called compilerOptions that is not allowed under any partial trust configuration. When you run the application in medium trust or another partial trust setting, ASP.NET will raise an error noting that "the current trust level does not allow the use of the 'compilerOptions' attribute". NOTE: Depending on the security settings of your server, this error message may or may not be visible to you.
To resolve this issue:
To avoid this problem, you can remove
the compilerOptions setting, as well as the warningLevel setting, from this configuration
section in your application’s web.config file after you have created or migrated
your application. After making the change, your
<system.codedom>
<compilers>
<compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
<providerOption name="CompilerVersion" value="v3.5"/>
</compiler>
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
<providerOption name="CompilerVersion" value="v3.5"/>
</compiler>
</system.codedom>
The workaround above also has the following impact on your ASP.NET Web applications:
1. For websites built with Visual Basic, the workaround prevents using the new LINQ capabilities of .NET Framework 3.5 on an ASP.NET page. To fix this, users can add the following line to the beginning of their Visual Basic codebehind file, and any other Visual Basic code files that use LINQ:
Option Infer On
Inline Visual Basic inside the .aspx or .ascx page (within a <script runat=”server”> tag) will not be able to use LINQ with this workaround. Users should move this code to a codebehind file. Other ASP.NET page features that use LINQ, such as the LinqDataSource control, will continue to work normally.
2. For websites built with C#, compiler warnings will no longer show up in the Visual Studio errors pane on compilation.
The wcfSvcchost.exe tool requires administrator permissions to run. The WCF service library template in Visual Studio 2008 will not run correctly if wcfSvchost.exe is not available.
To resolve this issue:
Run Visual Studio 2008 using an Administrator account when you author services that use wcfSvchost.exe. In Windows Vista, right-click the Visual Studio 2008 icon and then click "Run as administrator."
The WCF samples setup script Setupvroot.bat does not work on Windows Vista if the NetMsmqActivator service is enabled and Message Queuing (MSMQ) is not installed. The iisreset utility does not work unless MSMQ is installed or the NetMsmqActivator service is disabled. The WCF samples setup script Setupvroot.bat will not run unless MSMQ is installed or the NetMsmqActivator service is disabled.
To resolve this issue:
Make sure that MSMQ is installed or disabled the NetMsmqActivator service on Windows Vista before you run the WCF samples setup script Setupvroot.bat.
The following WCF samples do not build or run correctly in Visual Studio 2008:
- TechnologySamples\Scenario\DataBinding\WPF (does not build)
- TechnologySamples\Scenario\RestPox (builds but fails to run on Windows Vista)
- TechnologySamples\Extensibility\Transport\UdpActivation (builds but fails to run)
To resolve this issue:
- TechnologySamples\Scenario\DataBinding\WPF
This issue affects only the C# version of the sample. To resolve, remove the following string from client.csproj: "<UICulture>en-us</UICulture>".
- TechnologySamples\Scenario\RestPox
This issue affects both the C# and Visual Basic versions of the sample when they are run on Windows Vista. The client runs correctly almost all the way through the sample, then fails near the end. To resolve the issue, remove the forward slash from the following lines of code:
links.Add( new Uri( message.Properties.Via + "/" + customerId ) ) in file CustomerService.cs
links.Add( New Uri(msg.Properties.Via.ToString() & "/" & customerId ) ) in file CustomerService.vb
- TechnologySamples\Extensibility\Transport\UdpActivation
No workaround is available.
This issue occurs when you create a Web site by using Visual Studio 2008 and choose either the HTTP or FTP hosting option instead of the default File System option. If you add a WCF Service to the site by using the Add New Item command, the service is added but may not work as expected.
To resolve this issue:
Use one of the following workarounds to resolve the issue:
- Use the ASP.NET Web Application or a WCF Service Application project type instead of a Web Site solution.
- Use the File System hosting option instead of HTTP or FTP.
- If you must use a Web site with HTTP or FTP, you can add the WCF Service and then modify the resulting web.config file as follows. The <system.servicemodel> contains a <services> element. You must remove the namespace information from each <service> element and <endpoint> element. For example:
Original generated configuration
<services>
<service name="Namespace.ServiceName">
<endpoint contract="Namespace.ServiceName"/>
</service>
</services>
Fixed configuration
<services>
<service name="ServiceName">
<endpoint contract="ServiceName" />
</service>
</services>
Using a Web site or Web application over a Remote Desktop as non-Admin will automatically enable NTLM authentication. Therefore, when an ASMX or WCF service is consumed, the following error occurs: "The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'NTLM'."
To resolve this issue:
1. Open the property pages for the Websites
2. On the Start Options tab, clear NTLM Authentication
Note: We advise this
only for Web sites that exclusively have WCF services. WCF services security is managed through the configuration in the web.config file, which makes NTLM Authentication unnecessary.
Using the "Discover" button on the Add Service Reference dialog box does not display services in the same solution in WCF projects created from non-Web based templates.
To resolve this issue:
- Build and run the WCF Service Library without debugging. When Autohost has hosted the service, right-click the Service in the Autohost and then click Copy Metadata Address to get the service address. Paste the address in the Add Service Reference dialog box to add a reference to the service.
- Alternatively, use the "Discover" button to find services from projects that are based on the WCF Web site template or WCF Service Application template.
Stepping into or hitting breakpoints in a WCF Service Application from another project with a Service Reference works the first time only.
To resolve this issue:
Open the Options dialog box and select "Show all settings". Expand the Projects and Solutions node and then select Build and Run. Clear "Only build startup projects and dependencies on Run".
Running some WCF-based project templates starts the service in WCF Service Host and opens a test form to debug operations on the service. Because of a signing problem, this results in a crash of svcutil.exe and the test form does not work.
To resolve this issue:
Disable strong name signing for svcutil.exe by opening a Visual Studio Command Prompt. At the command prompt run: sn -Vr "<program files>\Microsoft SDKs\Windows\v6.0A\Bin\SvcUtil.exe" (replace <program files> with your program files path - ex: c:\Program Files)
By default, a WCF proxy is generated in Visual Studio 2008 for Web Services for projects that target .NET Framework 3.0 or 3.5. Attempting to call an ASMX WebService method that returns a typed datatype results in a error.
To resolve this issue:
Add a Web Reference that generates an ASMX proxy instead of a Service Reference that generates a WCF proxy. To do this on new projects that target .NET Framework 3.0 or 3.5, click Add Service Reference on the Project menu or on the project shortcut menu. In the dialog box, click Advanced, and then click Add Web Reference and add the Web Reference.
The SvcUtil.exe tool can generate code for Web service clients and data types from metadata in any language that has a managed code provider. SvcUtil.exe has been tested with the C#, Visual Basic, and C++ managed code providers. Other code providers have not been tested and may generate code that does not compile or may be otherwise unusable.
To resolve this issue:
No workaround is available.
You can use the SvcUtil.exe tool to generate code for Web service clients and data types from metadata. However, there are known issues with the C++ code provider in Visual Studio 2008 Beta 2 that can cause the tool to generate Managed C++ code that may not compile.
To resolve this issue:
Manually alter the generated code to resolve any compiler errors.
An example at the end of the Svcutil.exe help output indicates that you can use the /dataContractOnly (/dconly) option to generate data contracts from a running service:
svcutil.exe /dconly http://service/metadataEndpoint
- Generate Data Contract types from a running service or online metadata documents.
This usage does not work. You can only use the /dconly option to generate data contracts from local metadata files.
To resolve this issue:
Download the metadata from the running service by running the following command:
svcutil.exe /target:metadata http://service/metadataEndpoint
Run svcutil with the /dconly option on the downloaded metadata files, as follows:
svcutil.exe /dconly *.wsdl *.xsd
If you create a Web site in Visual Basic, add an AJAX-enabled item template to the website, and then add the WebGet() attribute to the service, the application does not build.
To resolve this issue:
Manually add the statement Import System.ServiceModel.Web to the source code of the WCF service interface file named Service#.vb in the Web site or Service#.svc.vb in the Web application. Alternatively, you can open the project property page and click System.ServiceModel.Web in the Imported namespaces section of the Reference page.
If you create a non-WCF Visual Basic project, Web or Windows type, and then add a WCF Service item to this project, then the project build fails with an error message stating that ServiceContract and OperationContract are not defined. This occurs because System.ServiceModel is not imported when items are added to a Visual Basic project.
To resolve this issue:
Manually add the statement Import System.ServiceModel to the source code of the WCF service interface file IService#.vb.
Alternatively, open the property page for the project using the shortcut menu, and then click System.ServiceModel in the Imported namespaces section of the Reference page.
If you create a WAP project, and then add an item to this project, then two WCF Service item templates appear in the Add New Item dialog box. One is for a WAP project with the name Service#.svc, the other is for an ordinary project with the name Service#.cs or Service#.vb.
To resolve this issue:
Select the WCF Service item template that has the name Servicex.svc in the Add New Item dialog box.
Solutions and projects created in Visual Studio 2008 Beta 2 can be opened and edited in Expression Blend, but solutions and projects will not build.
Additionally, when you open Expression Blend projects in Visual Studio 2008 they will be upgraded to the Visual Studio 2008 format. When this upgrade is complete, the project will no longer build in Expression Blend. You can still open and edit the project in Expression Blend, but the project will not build in Expression Blend.
To resolve this issue:
- Use the Expression Blend 2 August Preview
- To resolve this issue for Expression Blend:
Apply the following workaround (one-time only). Note that the workaround is only applicable if Visual Studio 2008 Beta 2 is installed. A tool to facilitate this is available here: http://blogs.msdn.com/expression/archive/2007/05/29/working-with-visual-studio-code-name-orcas-and-expression-blend.aspx
1. Close Expression Blend.
2. Navigate to \Program Files\Microsoft Expression\Blend 1.0\.
3. Create a new .xml file in that folder and rename the file to Blend.exe.config
4. Copy and paste the following XML snippet into that file.
<?xml version ="1.0"?>
<configuration>
<startup>
<supportedRuntime version="v2.0.50727"safemode="true"/>
<requiredRuntime version="v2.0.50727" safemode="true"/>
</startup>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Microsoft.Build.Framework" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-99.9.9.9" newVersion="3.5.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.Build.Engine" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-99.9.9.9" newVersion="3.5.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
5. Save the changes to the file and close it.
6. Start Expression Blend. You should be able to successfully build your projects and solutions.
Note: If you uninstall Visual Studio 2008 and .NET Framework 3.5, you should also delete the Blend.exe.config file.
For latest information about limitations and issues when the WPF designer is used in Visual Studio 2008 Beta 2, see the Cider wiki on Channel9, http://go.microsoft.com/fwlink/?LinkId=83541
2.3.8.3 Property Browser performs object to string and string to object conversion by using the en-US culture.
When using the WPF Designer Property Browser to view objects as strings or to enter strings that are converted to an object, the Property Browser will match the XAML convention of using the en-US CultureInfo.
To resolve this issue:
When a string is entered int the Property Browser, that string is converted to an object through a TypeConverter. Likewise, a TypeConverter is used to display a string representation of an object. The WPF TypeConverters only fully support the en-US culture because that is the only culture that XAML supports.
To be consistent with XAML and to reuse the WPF TypeConverters, the WPF Designer Property Browser will display and parse all strings by using the en-US culture only.
Note: String Content does not go through conversion and will not be affected.
Cannot move, resize, or select controls, and also cannot interact with designer features on the WPF Designer design view with a Tablet PC pen.
To resolve this issue:
There is no workaround other than using a mouse.
Adding a customer control to the designer from the Toolbox fails because there is a space in the path to the assembly for that control.
To resolve this issue:
Use a path that does not contain spaces.
If you edit very large XAML files in the WPF Designer ("Cider"), the designer will use large amounts of memory and CPU time.
To resolve this issue:
Avoid editing very large XAML files in the WPF Designer in Beta 2. Very large can be characterized as files over 150KB or files with over 1000 elements. An example is a XAML file of a vector drawing that contains large numbers of Path elements.
If a WPF project is built from the command line while that same project is open in Visual Studio 2008, that build will result in assemblies that are missing the BAML. Consequently, those assemblies will not work at run time and will cause the WPF designer to reload with errors.
To resolve this issue:
Rebuild in Visual Studio 2008.
When Workflow Foundation (WF) projects are built using the MSBuild toolset, the toolset version must match the project file schema.
To resolve this issue:
- If you are using an Visual
Studio 2008 project file, use the Visual
Studio 2008 build toolset.
- If you are using a Visual Studio 2005 project file, use the Visual Studio 2005 build toolset.
In Workflow Projects in Visual Studio 2008, if you are using Development Settings set to Visual C++ Development Settings, then custom activities are not visible in the Toolbox after the custom activity is compiled.
To resolve this issue:
1. To add the compiled custom activity to the Toolbox:
a. Right-click the Toolbox and then click Choose Items.
b. In the Choose Toolbox Items dialog box, click Browse, select the compiled assembly or executable file, and then click Open. c. Click OK. The custom activity now appears in the Toolbox.
-or- 2. Select one of the following Development settings instead of Visual C++ Development Settings: General Development Settings, Visual Basic Development Settings, Visual C# Development Settings, or Web Development Settings.
The utility "aspnet_merge.exe" is not signed with a strong name in Visual Studio 2008 Beta2. Attempting to run the utility generates the System.IO.FileLoadException:
Exception Details:
Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'aspnet_merge, Version=3.5.0.0, Culture=neutral, PublicKey
Token=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)
File name: 'aspnet_merge, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' ---> System.Security.SecurityException: Strong
name validation failed. (Exception from HRESULT: 0x8013141A)
To resolve this issue:
You must disable strong name verification checking for "aspnet_merge.exe". You can disable this by using the strong name utility "sn.exe".
1. Run the following as a local admin from the command prompt:
For a 32-bit computers, run:
"%ProgramFiles%\Microsoft SDKs\Windows\v6.0A\bin\sn.exe" -Vr "%ProgramFiles%\Microsoft SDKs\Windows\v6.0A\bin\aspnet_merge.exe"
For a 64-bit computers, run:
"%ProgramFiles%\Microsoft SDKs\Windows\v6.0A\bin\x64\sn.exe" -Vr "%ProgramFiles%\Microsoft SDKs\Windows\v6.0A\bin\x64\aspnet_merge.exe"
2. The following output indicates that the command ran successfully:
"Verification entry added for assembly 'aspnet_merge,B03F5F7F11D50A3A'"
3. Run "aspnet_merge.exe".
Some tools that are typically found in \Program Files\Microsoft SDKs\Windows\v6.0A\ are not installed with Visual Studio 2008. These tools are:
- UISpy.exe
- XAMLPad.exe
- Service Trace Viewer
- Mt.exe
- soapsudscode.dll
- sn.exe.config (x64 platforms only)
- gacutil.exe.config (x64 platforms only)
- Perflibmig.exe (x64 platforms only)
To resolve this issue:
These tools are available in the standalone Windows SDK. The Windows SDK is available here: http://go.microsoft.com/fwlink/?LinkId=94673
After Visual Studio 2008 is uninstalled, the Start menu shortcut for the Windows SDK for Visual Studio 2008 remains.
To resolve this issue:
Restart Windows.
Some Windows SDK tools do not install side-by-side. The version in \Program Files\Microsoft SDKs\Windows\v6.0A\Bin\ is the one that was installed with the most recently installed version of Visual Studio 2008 Beta 2.
To resolve this issue:
In the Add or Remove Programs, repair the version of Visual Studio 2008 Beta 2 in the language you want to use.
Previous versions of the Windows SDK may conflict with Visual Studio 2008 Beta 2. They should be uninstalled before Visual Studio 2008 Beta 2 is installed.
To resolve this issue:
The Windows SDK standalone can be downloaded here: http://go.microsoft.com/fwlink/?LinkId=94673
© 2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement