This document contains readme notes for the following
products:
·
1.1. Supported Architectures
·
1.2. Supported Operating Systems
·
1.3. Hardware
Requirements
·
2.1. Installing
·
2.1.1. General Issues
·
2.1.2. Visual C++ Express Edition
·
2.1.3. Visual C# Express Edition
·
2.1.4. Visual Basic Express Edition
·
2.1.5. Visual Web Developer Express
Edition
·
2.2. Uninstalling
·
2.2.1. General Issues
·
2.2.2. Visual C++ Express Edition
·
2.2.3. Visual C# Express Edition
·
2.2.4. Visual Basic Express Edition
·
2.2.5. Visual Web Developer Express
Edition
·
2.3. Product
Issues
·
2.3.1. General
Issues
·
2.3.2. Visual C++ Express Edition
·
2.3.3. Visual C# Express Edition
·
2.3.4. Visual Basic Express Edition
·
2.3.5. Visual Web Developer Express
Edition
·
x86
·
x64 (WOW)
1.2. Supported Operating Systems
·
Microsoft Windows XP Service Pack 2 or
Service Pack 3
·
Microsoft Windows Server 2003 Service Pack 2
·
Microsoft Windows Server 2008
·
Microsoft Windows Vista or Windows
Vista Service Pack 1
· Minimum: 1.6 GHz CPU, 192 MB RAM, 1024x768
display, 5400 RPM hard disk
·
Recommended: 2.2 GHz or higher CPU, 384 MB or
more RAM, 1280x1024 display, 7200 RPM or higher hard disk
·
On Windows Vista/Windows Server 2008:
2.4 GHz CPU, 768 MB RAM
·
1.3 GB of available disk space
for the full installation
When you try to install SQL Server 2008 RTM or SQL Server 2005 RTM/SP1/SP2 on Windows 7 RC, you may receive a warning message that SQL Server has known compatibility issues with this version of Windows. Because SQL Server is redistributed by Visual Studio, an installation in which the user selects to install SQL Server together with Visual Studio may be affected. The issues that trigger the compatibility warning have been fixed in SQL Server 2008 SP1 and SQL Server 2005 SP3.
To resolve this issue:
Install
Visual Studio together with SQL Server and then upgrade to SQL Server 2008 SP1 or SQL
Server 2005 SP3 by using Windows Update. As an alternative, you can install SQL
Server 2008 SP1 before you install Visual Studio.
The following steps are for installing Visual Basic 2008 Express Edition with SP1, together with SQL Server 2008, on Windows 7 RC. Other Express Editions can be installed the same way.
1. Download Microsoft Visual Basic 2008 Express Edition with SP1 from the Express Edition download page.
2. In Setup, make sure to select “Microsoft SQL Server 2008” on the “Optional Components” page.
3. When SQL Server 2008 installation starts, you will receive a compatibility warning message.
4. Select Run Program to continue the installation.
5. You will then get a second compatibility warning message. Select Run Program again.
6. After installation is completed, start Windows Update.
7. If you do not have Microsoft Update installed, click “Get updates for other Microsoft products. Find out more” and follow the instructions to install Microsoft Update.
8. Select Check for updates in the left-hand pane.
9. Under the optional updates, you should see “Microsoft SQL Server 2008 Service Pack 1”.
10. If “Microsoft SQL Server 2008 Service Pack 1” is not listed as an optional update, go here to download the service pack.
11. Select the box next to the entry and click OK.
12. Windows update will then install SQL Server 2008 SP1.
13. When installation is completed, you may be prompted to reboot.
More Information
If you are installing SQL Server 2005 Express (any Express edition) or SQL Server 2008 Express (Runtime Only), you can just download the SQL Server Express package that contains the latest service pack. This may seem counter-intuitive if you already have an Express package, but installing it and then downloading and applying a service pack takes longer than downloading and installing a package that already contains the latest service pack. Also, the SQL Server 2008 Express service pack package is actually bigger than the SQL Server Express package because the service pack is shared with all SQL Server 2008 editions.
· Download SQL Server 2008 Express SP1
· Download SQL Server 2005 Express Edition SP3
· Download SQL Server 2005 Express Advanced Edition SP3
· Download SQL Server 2005 Express Toolkit Edition SP3
· Download SQL Server 2005 SP3
· Download SQL Server 2008 SP1
If you have to install SQL Server 2008 Express edition other than Runtime Only on Windows 7 RC and want to avoid the warning messages, you can create the SQL Server 2008 with Service Pack 1 package yourself. Follow the steps described by Peter Saddow: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1
If you install either the Windows SDK for Windows Vista or the Windows SDK Update for Windows Vista, and then uninstall the Windows SDK, registry keys that are required by Visual Studio to find Windows headers, libraries, and tools are removed.
To resolve this issue:
Perform one of these tasks:
During installation of the Visual Studio 2008 Express
Edition SP1, MSDN Express Library for Visual Studio 2008 Express Edition SP1
will not be installed on the computer.
To resolve this issue:
MSDN Express Library for Visual Studio 2008 Express Edition
SP1 is available as a separate download on
the Microsoft Visual Studio Express Editions Web site www.microsoft.com/express/.
After installation of Visual Studio 2008 Express Edition with SP1 RTM on a computer on which Visual Studio 2008 Express Edition with SP1 Beta was previously installed, the end user licensing .txt file for the SQL Server Express 2008 bootstrapper is not removed when the final end user license agreement file in .rtf format is installed. The correct end user license agreement file (.rtf) for the SQL Server 2008 Express bootstrapper is the one that is deployed by ClickOnce. Subsequent uninstalls of Visual Studio 2008 Express Edition with SP1 RTM will remove the .rtf end user license file, but the .txt version will remain on the computer.
To resolve this issue:
The orphaned Eula.txt does not cause any operational issues. However, you can remove the orphaned Eula.txt file as follows:
1) Change directory to <drive>:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\SqlExpress2008\<lang>\ (e.g., for drive D and English, D:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\SqlExpress2008\en\)
2) Remove the Eula.txt file.
SQL Server Express 2008 RTM installation will fail when Visual Studio 2008 Express Edition with SP1 RTM is installed on a computer on which an earlier release of SQL Server Express 2008 is running.
To resolve this issue:
1. Open the Service Control Manager from Control Panel -> Administrative Tools.
2. Stop the "SQL Server (SQLEXPRESS)" service.
3. Set the start up type to Manual.
4. Install Visual Studio 2008 Express with SP1.
5. In the Service Control Manager, reset the start up type for the "SQL Server (SQLEXPRESS)" service to Automatic.
6. Start the service.
During installation of Visual Studio 2008 Express Edition with
SP1, if the option to install SQL Server Express is selected, the SQL Server
Express instance will not be installed/upgraded
if the SQL Server Express installed on the computer is a different
language than the language of the Visual Studio 2008 Express Edition with SP1
that is being installed. For example, if the target computer has an
English version of SQL Server Express 2005 or a pre-release version of SQL
Server Express 2008 installed and you are installing the Japanese version of
Visual Studio 2008 Express Edition with SP1, then SQL Server Express will not
be updated because the language versions do not match.
To resolve this issue:
To resolve this issue, install the language version of
Visual Studio 2008 Express Edition with SP1 that matches the language version
of the SQL Server Express product on the computer, or remove the SQL Server
Express product from the computer before you install Visual Studio 2008 Express
Edition with SP1.
.NET Framework 2.0 SP2 installation fails on a computer that has .NET Framework 2.0 or .NET Framework 2.0 SP1 installed and is running Windows XP, Windows Server 2003, or Windows 2000.
The .NET Framework 2.0 SP2 Setup uninstalls earlier versions of the .NET Framework 2.0 and .NET Framework 2.0 SP1. When Windows Installer uninstalls earlier versions, it uses the cached installation database. During the uninstall operation, if Windows Installer cannot find the installation packages for the earlier updates in its cache, or the original source location, the installation fails. If an incomplete rollback occurs, this failure to install may also cause applications that use the .NET Framework to fail.
This problem may occur for either of these reasons:
The Windows Installer cache is missing required files.
The Windows Installer cache has been changed. The cache is
critical for repairing, for updating, and for uninstalling products. Therefore,
do not remove or modify the contents of the cache. If you change the contents
of the cache, you may be prompted for a source when you try to update or to
repair Windows Installer-based products.
Sometimes a Windows Installer Patch (.msp)
file that Windows Installer expects to find in the cache may not exist. The
following are two common reasons why the .msp file
may be missing:
- A tool that finds and deletes large files or rarely used
files on the hard disk has been run.
- The owner of the %windir%\Installer
directory is changed from SYSTEM or from Administrators.
If this issue occurs, the Windows Installer log for the
failing installation will show something that resembles the following:
MSI (s) (D0:B0) [19:05:57:843]: Couldn't find local patch
'C:\WINDOWS\Installer\a4784a.msp'. Looking
for it at its source.
MSI (s) (D0:B0) [19:05:57:843]: Resolving Patch source.
You can use the Microsoft .NET Framework Registration
Correction Tool to resolve this issue when it occurs. The tool fixes this issue
by deleting all hotfix or update registrations that
are specific to this update so that maintenance installations do not try to
load the specific .msp file.
You can also try to fix this issue by rebuilding the
installer cache. You can typically find the Knowledge Base number for the hotfix or for the update in the lines that follow
"Resolving Patch source," as shown in the following example:
MSI (s) (D0:B0) [19:05:57:859]: SOURCEMGMT: Source is
invalid due to missing/inaccessible package.
MSI (s) (D0:B0) [19:05:57:859]: Note: 1: 1706 2:
-2147483647 3: NDP20-KB917283-X86.msp
To fix the Windows Installer Cache for this example, follow
these steps:
1. Visit the following Microsoft Web site:
http://support.microsoft.com/kb/917283 (http://support.microsoft.com/kb/917283).
Note: You can replace the Knowledge Base article number in the URL with the
Knowledge Base article number of the hotfix or the
update for which you want to fix the Windows Installer cache.
2. Download the update.
3. Extract the .msp file in the hotfix or the update by using the /x command-line switch or
the /extract command-line switch.
4. Copy the extracted .msp file
to the location for the missing file. In this example, the location is %windir%\Installer\a4784a.msp.
The hotfix registration or the
update registration may be corrupted.
After a hotfix or an update is
installed on a Windows Installer-based product, the hotfix
registration or the update registration may become corrupted. This problem can occur
because of third-party registry cleaner utilities that remove certain registry
keys. These keys include the keys that are meant for internal use by Windows
Installer. In this case, the "Resolving Patch source" message in the
log reads as follows:
MSI (s) (CC:5C) [03:02:56:181]:
Couldn't find local patch ''. Looking for it at its source.
MSI (s) (CC:5C) [03:02:56:181]:
Resolving Patch source.
Note: The location of the hotfix or the update is missing in the log message because
of the missing hotfix or upate
registration information. In this case, a hotfix or
an update is still registered to a product. However, location information for
the hotfix or update is missing. Although the file
may exist, Windows Installer does not know the path of the file that Windows
Installer requires to load.
You can use the Microsoft .NET Framework Registration
Correction Tool to resolve this issue when it occurs. The tool fixes this issue
by deleting all hotfix or update registration that is
specific to this service pack so that maintenance installations do not try to
load the hotfix or the update package.
To resolve this issue:
If you cannot successfully install .NET Framework 2.0 SP2
and find the "Resolving Patch source" text in the installation log
file as described in the “Cause” section, you can
download the Microsoft .NET Framework Registration Correction Tool to resolve
this issue.
Microsoft .NET Framework 2.0 Registration Correction Tool
The Microsoft .NET Framework Registration Correction Tool
resolves both of the issues that the "Cause" section describes.
The following file is available for download on the
Microsoft Download Center:
Download the Microsoft .NET Framework 2.0 Registration
Correction Tool package now. http://www.microsoft.com/downloads/details.aspx?FamilyID=0BA6038C-061E-4B4A-9BE9-96A323701260
The Microsoft Download Center has one version of the tool for each processor architecture that the .NET Framework 2.0
supports (x86, x64, and IA-64). Most customers run a 32-bit version of the
operating system. Therefore, these customers should download and install the
x86 version of the tool.
Administrators may also use this utility in scripts by
passing either the /q command-line switch or the /quiet command-line switch. In
this way, you can run the application in silent mode without using a user
interface and without using block scripts.
The tool writes a running log under the %TEMP%\dd_clwireg.txt
folder. You can view this log for more information about what the tool is
doing.
Notes
- The Microsoft .NET Framework Registration Correction Tool
is designed to be used with any current version of the .NET Framework.
- You must be an administrator to run this utility.
A Windows Automatic Update notification to restart the computer may appear when Visual Studio 2008 Express Edition with SP1 is being installed on a Windows Vista computer that does not have .NET Framework 2.0 SP2 and .NET Framework 3.0 SP2 installed. Allowing Windows Update to restart immediately will cause Visual Studio Setup to fail.
To resolve this issue:
Postpone the restart until the Visual Studio Express Edition with SP1 installation is finished, or the Visual Studio 2008 Express Edition Setup prompts to restart computer.
Visual Studio 2008 Express Edition SP1 Setup may fail to install Microsoft Windows Installer 4.5 on Windows Vista computers when a reboot is pending before Visual Studio Express Edition Setup starts. Windows Installer 4.5 is required for SQL Server 2008 setup and will be installed when SQL Express is selected. Windows Vista updates that have a pending reboot may cause Express Setup to prompt for a reboot before all components are installed. When Setup is resumed after reboot, Windows Installer 4.5 Setup fails.
To resolve this issue:
1. Visit Microsoft Windows Update to ensure that Windows is up-to-date
on critical and important updates.
2. Re-launch Visual Studio 2008 Express Edition SP1 Setup.
3. Select Add Optional Components.
4. Select SQL Server Express.
5. Click Next to install selected add-on products.
Setup will download and install Windows Installer 4.5 if it is not already installed.
6. Click Reboot Now if prompted to reboot after
Windows Installer Setup.
7. Let Setup finish installing SQL Server Express.
Visual Studio 2008 Express Edition SP1 Setup may report that the Windows Installer service is unavailable when Setup resumes after a reboot.
This is typically a timing issue on some computers when the Windows Installer service starts late in the boot process, after Visual Studio Setup has already resumed.
To resolve this issue:
1. Click OK in the error dialog box.
2. Manually re-launch Visual Studio 2008 Express Edition SP1 Setup.
3. Select Add Optional Components if Express Edition Setup starts in a maintenance mode, then select the features you want to add.
During Visual Studio Express Edition installation, you may be prompted to reboot your computer before all components have been installed. Typically this happens if you are installing MSI 4.5 and SQL Server Express 2008 because a reboot is required before SQL Server Express 2008 installation can begin. If "Reboot Later" is selected, Setup will not be restarted automatically after the computer has rebooted and you may have to rerun Setup to complete the installation of all components.
To resolve this issue:
Reboot the computer and then restart the Setup for the Visual Studio 2008 Express Edition with Service Pack 1. You may have to select "Add Optional Components" and select "SQL Server Express 2008" to complete the SQL Server Express 2008 installation.
After an upgrade to Visual Studio 2008 Express Edition SP1 RTM (Japanese) from Visual Studio 2008 Express Edition SP1 Beta (Japanese), the ADO.NET Entity Data Model Designer is removed.
To resolve this issue:
Repair Visual Studio 2008 Express Edition SP1 RTM (Japanese) by using Add or Remove Programs (Windows Server 2003 and Windows XP) or Programs and Features (Windows Vista and Windows Server 2008).
When Visual Studio 2008 Express Edition with Service Pack 1 is being installed and the option to install SQL Server Express 2008 is selected, failures may occur with the installation of SQL Server Express 2008 RTM. The failure could be a result of any of a variety of conditions:
1) Upgrade failure caused by unsupported cross-language upgrades (for example, pre-RTM release of SQL Server Express 2008 English installed and attempting to upgrade to SQL Server Express 2008 Japanese RTM)
2) Failure due to unsupported upgrade path (for example, upgrading to SQL Server Express 2008 on a computer that has SQL Server Express 2005 with Advanced Services.)
3) A pending system reboot or a locked file during Visual Studio 2008 Express Edition SP1 Setup may cause installation of SQL Server 2008 Express to fail.
4) After a required reboot, the user logs into the computer by using a different logon name than the one that was used to run Setup of Visual Studio 2008 Express Edition with Service Pack 1 RTM. Therefore, after reboot, Setup does not resume and does not continue with installation of SQL Server Express 2008.
5) If, during installation, you select "Restart later" on the prompt to reboot before installation of SQL Server Express 2008, or if a reboot happens during the installation (triggered by something external to the installation, for example, you started the installation in the evening, Windows Update got an update during the night, and triggered an unattended reboot before the installation finished installing SQL Server Express 2008), installation of SQL Server Express 2008 will not occur.
To resolve this issue:
1) To work around this failure, you must install the upgrade to the same locale language as the pre-2008 RTM version of SQL Server Express previously installed.
For more information about upgrade of SQL Server Express 2008, see http://msdn.microsoft.com/en-us/library/ms143393(SQL.100).aspx.
2) There are two options to work around this scenario:
a. Manually upgrade the instance that is blocking. For example, download and install SQL Server Express Advanced 2008 independent of the installation of Visual Studio 2008 Express Edition with Service Pack 1 RTM; or
b. Remove the instance of SQL Server that is blocking installation of SQL Server Express 2008 and then re-run the Setup for Visual Studio 2008 Express Edition with Service Pack 1 RTM.
For more information, see http://msdn.microsoft.com/en-us/library/ms143393(SQL.100).aspx
3) Reboot the computer and then re-start the Setup for the Visual Studio 2008 Express Edition SP1. On the maintenance screen, choose Add Optional Components, and then select SQL Server Express 2008.
4) After reboot, ensure that you log on the computer by using the same user name that you used to initially run Setup for Visual Studio 2008 Express Edition with Service Pack 1 RTM.
There are no known issues.
There are no known issues.
There are no known issues.
When you upgrade from Visual Web Developer Express Edition 2008 to Visual Web Developer Express Edition 2008 SP1, IDE settings will be reset to the new SP1 defaults. These IDE settings include customizations to the menus, toolbars, tool windows, editor options, fonts and colors, key bindings, and so on. You can back up your settings before you install SP1 by using the Import and Export Settings wizard to export your current settings. The following changes have been made to the Visual Web Developer Express Edition with SP1 defaults:
- Added "New Project" and "Open Project" to the File
menu
- Added "New Project" and "Open Project" to the toolbar
- Added "CSS" and "CSS Styling" options pages to
"Tools | Options" when "Show all settings" is cleared
- Added "Open Project" and "Create Project" to the Start
Page
To resolve this issue:
To maintain your IDE settings:
1. Before you install Visual Web Developer Express Edition with SP1, open your existing installation and go to "Tools | Import and Export Settings".
2. Select "Export selected environment settings".
3. Click "Next".
4. Choose the settings you want to export (Note: If you export "Menu and Command Bar Customization", "Simplified Tools/Options" or "Start Page Commands" under "General Settings" and then import them in Visual Web Developer Express Edition with SP1, some of the settings added in SP1 will be overwritten.)
5. Choose a file location to save your settings.
6. Install Visual Web Developer Express Edition with SP1.
7. In Visual Web Developer Express Edition with SP1, go to "Tools | Import and Export Settings".
8. Select "Import selected environment settings".
9. Click "Next".
10. Choose "No, just import new settings, overwriting my current settings". (You do not have to back up the default settings because you can "Reset all settings" later.)
11. Select the settings file you exported in step 5.
12. Click "Finish".
13. To see "New Project" and "Open Project" on the File menu, you must manually add these commands to the menu by right-clicking the File menu, clicking "Customize...", selecting the "Commands" tab, selecting the "File" category, and then dragging the "New Project" and "Open Project" to the File menu and "Add New Project" and "Add Existing Project" to the File | Add submenu.
If you do not back up your settings before you install Visual Web Developer Express Edition with SP1, they cannot be recovered.
There are no known issues.
There are no known issues.
There are no known issues.
There are no known issues.
There are no known issues.
The integrated development environment (IDE) may report package load failures after non-matching language versions of different Visual Studio Express Editions are installed. This occurs when the user interface language of Windows and that of one of the Express Editions do not match (for example, Japanese Visual Basic Express Edition + English Visual Web Developer Express Edition on Japanese Windows) and the non-matching edition (Visual Web Developer in the example) is opened. The IDE attempts to load Japanese resources for English Visual Web Developer Express Edition and throws package load failure errors when they are not found. This is because the language setting for the IDE is automatically changed from 'Japanese (Japan)' to 'Same as Microsoft Windows' when the second language edition is installed even though they are separate SKUs that have separate executables.
To resolve this issue:
The International Settings page lets you change the default
language when you have more than one language version of a Visual Studio
Express Edition installed on the computer. To access this dialog box:
Â
Any changes you make on this page apply only to the default
IDE and do not take effect until the environment is restarted.
This issue shows in two scenarios:
- After Update Model from Database is run, associations are created for new foreign keys in the database but do not appear in the diagram.
- After undo/redo operations in the designer, association lines appear incorrectly placed in the diagram.
To resolve this issue:
There are several workarounds:
- Save the file. Close the designer. Open the file again.
- Right-click an empty area of the diagram and then click "Layout Diagram". This may alter manual layout changes previously made to the diagram.
- Manually move related entities to refresh their rendering.
The Properties window in the WPF Designer displays and edits values by using the U.S. format. This matches the XAML convention, which uses the en-US CultureInfo. For example, dates and numbers are always in U.S. format. Dates are always displayed mm/dd/yy. If you enter a date value in the Properties window it will be converted to the mm/dd/yy format.
To resolve this issue:
No workaround is available.
In Visual Studio 2008 SP1, if you use code Refactor to make type or member modifications, the refactoring will propagate to the XAML files. For more information about this feature, see "How to: Rename a Symbol that is Declared in XAML" in the documentation. The following limitations apply to this new feature:
- Refactoring will only change the XAML files in the current project and will not be applied across all of the projects in the solution.
- Refactor can be used only on type names and certain attributes. Refactor cannot be used on the following:
o The Setter Property attribute
o The TemplateBinding path attribute
o The Binding path and ElementName attributes
o The MethodName property of ObjectDataProvider
To resolve this issue:
Complete the modifications manually; for example, by using Find and Replace.
If you change a type or member in a XAML file, those changes will not propagate to the code files.
For example, if you change the name of a Button, which has event handlers associated with it, from the XAML editor, the code behind will not be updated.
To resolve this issue:
Modifications to code files must be made manually; for example, by using Find and Replace.
In Solution Explorer, if you right-click a XAML file, click Rename, and then rename the file, the file name will be changed, but there will not be any prompt to refactor the class name in XAML or the code behind. In particular, if you rename the XAML file that is referenced by the StartupUri property in the Application XAML file (for example, if you change Window1.xaml to MainWindow.xaml), then you must manually change the StartupUri property.
To resolve this issue:
Modifications must be made manually; for example, by using Find and Replace.
In a code-behind file, you can find all references to a symbol by right-clicking the symbol and then clicking Find All References. Find All References will not find XAML elements that do not have their Name property set.
Example:
The following XAML shows the MyUserControl element, which does not have a name:
<Grid>
<MyUserControl/>
(...)
In the code-behind file, if you right-click the MyUserControl symbol and select Find All References, only references in code will be found, and not in XAML.
To resolve this issue:
Name the control or search manually by using Find in Files.
If
you bind to an ObjectDataProvider through XAML and the ObjectDataProvider makes a call to a database, when you
load the XAML in the WPF Designer, the operation can be very long and
memory-intensive. As a result, the WPF Designer may stop responding until the
operation is finished.
To resolve this
issue:
Avoid setting up an ObjectDataProvider in this way at design time.
Programmatically, use the DesignerProperties.IsInDesignMode() method only to perform long or memory-intensive work at
run time.
When you open a WPF project
for the first time in a localized version of Visual Basic 2008 Express Edition
with SP1 or Visual C# 2008 Express Edition with SP1, the WPF Designer
may fail to load.
To resolve this
issue:
Close and re-open the
development environment.
There is a known issue in Visual Studio 2008 SP1 in
which the WPF Designer fails to load if a Binding uses RelativeSource
TemplatedParent without a Path.
For example:
<RepeatButton
Command="{x:Static ScrollBar.LineUpCommand}"
CommandTarget="{Binding RelativeSource={RelativeSource TemplatedParent}}"
/>
To resolve this
issue:
Specify a Path by
using the "." notation, which resolves to the same object.
For example:
<RepeatButton Command="{x:Static
ScrollBar.LineUpCommand}" CommandTarget="{Binding
RelativeSource={RelativeSource
TemplatedParent}, Path=.}" />
The
publish.htm page is generated without the script that detects the presence of
the .NET Framework Client Profile on target computers.
To resolve this
issue:
1. Ensure that the application targets the Client-only
Framework subset.
For Visual Basic projects:
Open project properties (double-click 'My Project' in
Solution Explorer).
Click the Compile tab.
Click Advanced Compile Options.
Select the 'Client-only Framework subset' option.
For C# projects:.
Open project properties (double-click 'Properties' in Solution
Explorer).
Click the Application tab.
Select the 'Client-only Framework subset' option.
2. To get the correct script, select the .NET Framework 3.5
SP1 prerequisite and publish the application.
3. In the Publish properties of the project, change the
prerequisite package back to the .NET Framework Client Profile and clear the
option "Automatically generate deployment web page after every publish.".
4. Publish the application again.
ClickOnce does not automatically check for SP1 if you selected the
option to target the .NET Framework Client Profile during development, even if
you add a reference to System.Data.Entity (which
requires SP1). If you clear the "Client-only Framework subset" option
in projects that contain a reference to System.Data.Entity,
the application will incorrectly check for .NET Framework 3.5 without SP1.
To resolve this
issue:
To force a check for .NET Framework 3.5 SP1:
For Visual Basic projects:
For C# projects:
WPF Designer may
crash if you reference values from a stand-alone or an external resource
dictionary as follows:
- The stand-alone dictionary has resource references between items in this same
dictionary (for example, style referencing a color),
- And you have an open project file (Window, etc) that references a value from
this stand-alone resource dictionary,
- And you modify a value in the stand-alone resource dictionary.
To resolve this
issue:
Close any open
documents that reference values from the dictionary before the dictionary is
updated.
The Assembly Cache
Viewer (Shfusion.dll) is a Windows shell extension that lets you view and manipulate the contents of the global assembly cache by
using Windows Explorer. Shfusion.dll is located in the %windir%\Microsoft.NET\Framework\v2.0.50727
directory.
In Windows Vista,
the Assembly Cache Viewer does not run with elevated permissions even if you
run it from a Command Prompt window that has elevated permissions (for example,
by using the START command with the path of the global assembly cache). This is
because the Assembly Cache Viewer is a shell extension for Windows Explorer,
which does not run with elevated permissions.
To resolve this
issue:
Use Shfusion.dll
only for viewing.
For updates, open a
Command Prompt window that has administrative privileges, and then use the
Gacutil.exe command-line tool from the .NET Framework SDK.
Because SQL Server
2008 Express Edition is not compatible with the Visual Studio 2005 Express
Editions, upgrading to SQL Server 2008 Express Edition will
overwrite the named instance of the database, and any of the Visual Studio 2005
Express Editions will no longer be able to target the default SQL Server
Express instance.
To resolve this
issue:
Visual Studio 2005
Express Editions are not compatible with SQL Server 2008 Express Edition.
Users must upgrade to the Visual Studio 2008 Express Editions in
order to develop SQL database-driven applications.
There
are no known issues.
There
are no known issues.
There
are no known issues.
When
you create a Web application project in Visual Web Developer Express Edition,
if you choose Add New Item in this project, the WCF Service item template is
found in the Web node, but not in the root node.
To resolve this
issue:
Use
the WCF Service Web application item template, located in the Web node.
Visual Studio 2008 SP1
Readme
Microsoft .NET Framework
3.5 SP1 Readme
© 2008 Microsoft Corporation. All rights reserved. Terms of Use
| Trademarks | Privacy Statement