Joy's WebLog

These two updates got released as High Priority Update, but it failed in lots of machine. I worked and got response from few of them where they tried the temporary fix that is uninstalling and reinstalling the Framework. Microsoft Team is already working to find if there is any other way we can fix this or to drill the actual root cause of the issue. The people with whom I worked provided the below steps and the response was positive.

After checking the various problem description, it looks like the existing version of the framework is also corrupted and due to which the installation is failing. I am listing few steps please perform and let me know the result of the same.

· http://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-fdaa79a8ac3d/dotnetfx35.exe

· The above will download the complete redistributable of Framework 3.5 SP1

· The next link I am providing is to remove the previous versions of Framework. I will recommend you cleaning the Framework from 3.5 followed by previous version

· http://blogs.msdn.com/joy/attachment/8764623.ashx

· Once the cleanup is done reboot the computer and install the framework redistributable downloaded

Once again I would like to add the above resolution is temporary and Microsoft is working getting more details and the root cause of the failure from the information we collected.

In Microsoft connect you will see a Visual Studio 2008 Clean Up tool is available for download. In couple of forum discussion and the query I have received whether that also removes Beta Version. Beta Version cannot be removed using this tool.

Before you conclude to the part that Visual Studio 2008 Cleanup Tool can remove the Beta Version, please take some time to go through the statement mentioned in Microsoft Connect

Note: Microsoft Visual Studio 2008 RC/RTM uninstall tool will not uninstall Microsoft Visual Studio 2008 Beta releases. To completely uninstall Microsoft Visual Studio 2008 Beta releases, Go to Add/Remove programs and uninstall Microsoft Visual Studio 2008 core component corresponding to Visual Studio Edition installed on your computer. For example, If you installed Visual Studio 2008 Team System Beta2, you can uninstall “Microsoft Visual Studio 2008 – Team Suite”. This would uninstall Visual Studio 2008 Beta components that need to be uninstalled prior to installation of Visual Studio final release.

Refer Download section to get the tool and also take some time to go through REFERENCE

Visual Studio 2010 makes easy Web, Cloud Development

When Visual Studio 2008 released last year, it was packed with a lot new functionality and features that made many a Microsoft developer's heart go a flutter.

This month, Microsoft unveiled the future of Visual Studio and its called Visual Studio 2010 or Dev10. To along with the new version, the .Net framework is being upgraded to

Major Changes in Visual Studio 2010

Enabling Emerging Trends

· Cloud Development: Windows Azure Tools for Visual Studio enables developers to build, debug and deploy services and applications for the cloud. This includes a project model that you can use to build your application or service. The Windows Azure Tools are used to deploy the package to the cloud through the Live Developer Portal.

· Parallel Development It's not easy by any means to write code that is optimized to run across more than one processor (parallel development). Microsoft now provides an environment that will help do this through Visual Studio IDE support for Parallel development and Native C++ libraries and compiler support for parallel applications. In addition, version 4 of the .net framework will also provide things like P-LIINQ and parallel language semantics and framework components. The debugger and a performance analyzer are also optimized to support parallel development.

Inspiring Developer Delight

· Coding Improvements: A new editor uses Windows Presentation Foundation technology to provide integrated support that helps you understand your code. Things like the “Document Map Margin” — which renders a graphical view of your source file with information about the code, third party add-ons for custom views, “Inline Call Hierarchy” — see how a particular method or entity is passed into and out of the code section, and “Highlight References” — a visual representation of code references.
The new editor also integrates with something called the TDD — Test Driver Development. The TDD is used to build the tests to test the code before it's even written.

· Web Development: A new set of ASP.Net tools allows developers to use TDD to build Model-View-Controller (MVC) based websites.
Included are Project Templates and Solutions out of the box for a MVC website, automatic generation of test projects, wizards for common tasks such as creating views from controllers and more. Support for Javascript and JQuery, a “one click” deployment wizard and SilverLight runtime and tooling are also new.

· C++ Development: A total revamp of the IDE to support parallel development, cloud development, an MFC Class Wizard and stronger support for large solutions with thousands of files are in the new version of VS.

SharePoint Development in Visual Studio 2010

The Visual Studio Tools for SharePoint. Share

· The tools added include:

· View lists and other artefacts from SharePoint in Visual Studio

· New SharePoint Services Project file

· Visual Web Part Designer, web part project items

· Event Receivers for SharePoint, Wizards to select the event receiver

· ASPX Workflow Initiation form for Workflow Project

· SharePoint packaging explorer and editor

Riding the Next Generation Platform Wave

· Windows 7: VS2010 will support development for the new Windows 7 operating system which includes a number of new tools to develop new apps and make existing ones take advantage of the new features of the OS.

· Office Business Applications: First introduced with VS2005, the next version of VS will enable developers to build Office applications that span multiple versions of MS Office (32 or 64 bit) and deliver them as a single deployment package (again using that One Click Wizard we mentioned above). In addition, we see the introduction of designer support for building flexible UIs in either WPF or Fluent, improved data binding, integration of Office data sources using LINQ and integration of the Business Data Catalog.

Democratizing Application Lifecycle Management

The primary discussion around this new version is about the “democratizing of application life-cycle management (ALM)” using Visual Studio Team System (VSTS) 2010 — also called Rosario.

Architecture Lifecycle Diagram

· Modelling Tools: Using VSTS 2010 Architecture, both technical and non-technical users can work together to model business systems using either UML and DSL — this modelling capability is part of the Oslo modelling platform.

· Improved Efficiency Throughout the Test Cycle: New and improved testing features include the ability to eliminate non-reproducible bugs, fast setup and deployment of tests and the ability to ensure all code changes are tested.

· Improvements in Collaboration Capabilities: Team Foundation Server has been enhanced, enabling development teams to utilize agile development approaches, visualization tools for tracking changes and workflow-build tools that catch errors before the real trouble comes

Architecture Explorer

Visual Studio 2010 also provides a unified VSTS Development and Database product.

Getting to Visual Studio 2010

It's not out yet. You can try it out with the Visual Studio 2010 and .NET Framework 4.0 Community Technology Preview. The CTP release is available in English only as a Virtual PC image.

Apparently the plan is to roll VS 2010 in five phases, broken down similar to how they are described above and starting with Demo crating Application Lifecycle Management. In an interview with Information Week, Dave Mendlen, the company's director of marketing for developer tools said “Instead of gradually opening a fire hose of news, with this release we'll focus on individual themes,” [] “While transparency is a good thing in many circumstances, the perception [among developers] was that they were getting bombarded with information sort of constantly.”

And while we've heard this new version makes developing SharePoint applications much easier, we couldn't find any details on the Microsoft sites on how they'll make that happen — other than the MSDN blog referenced above.

You can get a little more information on Visual Studio 2010 on the product website or view some videos describing it on Microsoft's Channel 9 PDC2008 site.

Click Here to download Vs2010

VS2010-Download

1. Rights user is having to perform the installation

2. Operating System compatibility

3. Any specific Prerequisites

4. Is prerequisites are getting installed along with the application or needs to be install prior to that ( Depends from application to application )

5. When it comes to troubleshooting part we need to ensure the above check list first then we need to ensure what all other information do we have

a) Exact Error Message

b) Error Code (If Any)

c) When we get the error

d) Supported / Not Supported

e) Application what user is try to install or what error he is getting while trying to run the application

f) We need to ensure we have enough data to troubleshoot the issue first

(The above scenario information can be consider for both .Net as well as Visual Studio installation)

6. Once we have these information we can proceed further

7. In both .Net & VS installation any failure we require the log file

8. Log file will guide to drill the issue further and we will have to consider both MSI and Non MSI log file

9. Error text file will be created by default or let’s say Error Log will be there in the Temp

10. But to get more deeper into that MSI log file helps

11. Either we can send the registry key to the customer or manually we can enable the verbose logging

12. To enable verbose logging: [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\Installer]

"EnableAdminTSRemote"=dword:00000001

"Logging"="voicewarmup!"

13. If we take a scenario of .Net installation the below logs should be in place to troubleshoot

a) dd_dpcheck_Netfx

b) dd_dotnetfxerror ( Version will also get listed)

c) dd_dotnetfxinstall (Version will also get listed)

d) MSI (verbose)

Best practice grabbing the correct log is to sort the temp folder with date and if there is several then better delete the entire temp and then try to install it again. This helps getting the fresh logs

14. Once we have these details we should logically proceed further

15. Known issue yes/No

16. Where the installation is failing

17. Is windows installer causing any issues? If yes we can always check with msiexec /unregister & maiexec /regserver

18. With the log we can also proceed further towards checking the below values:

19. We can also get lot of direction from common Windows Installer Error Messages

Ref: http://msdn.microsoft.com/en-us/library/aa372835(VS.85).aspx

Dealing with custom action failure for example we can always use process monitor which helps finding any access denied or we can say a overall process which are trying to get execute or registry which are being used

· These things will really help isolating the root cause and yes in Vista and Windows 2008 the Framework 2.0 and 3.0 it’s a OS component

· In case of repair you will have to go to “Windows Feature Turn On – Turn Off”

In case of any question or suggestion feel free to E Mail me. The above provided are basic steps to troubleshoot .Net Framework and if you are really not comfortable, my suggestion will be please contact us.

While trying to build C# application from command prompt Visual Studio Crashes

Event Type: Error

Event Source: Microsoft Visual Studio

Event Category: None

Event ID: 1000

Date: 7/16/2009

Time: 4:20:56 PM

User: N/A

Computer: G5PD2UA6010LLG

Description:

Faulting application devenv.exe, version 8.0.50727.762, stamp 45716759, faulting module ctpackage.dll, version 7.1.0.156, stamp 45420054, debug? 0, fault address 0x0003e511.

Root Cause of the issue: While building in VS2005, it crashes in CTPACKAGE.dll. This is IBM ClearCase dll and has know issues.

Resolution:

As per the IBM Knowledge Base we can update the particular version of the ClearCase Installed or we can remove the ClearCase

Refer To IBM Knowledge Base

Not able to install Framework 3.5 SP1

     Error Message

     Log:

[05/23/09,15:46:18] Microsoft .NET Framework 2.0a: [2] Error: Installation failed for component Microsoft .NET Framework 2.0a. MSI returned error code 1625

[05/23/09,15:47:23] WapUI: [2] DepCheck indicates Microsoft .NET Framework 2.0a is not installed.

[05/25/09,17:15:10] Microsoft .NET Framework 2.0a: [2] Error: Installation failed for component Microsoft .NET Framework 2.0a. MSI returned error code 1625

== Error code 1625 states about DisablePatch

== Check the target value of HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

== Patch was set to 1 but changed it to 0

== This means it will fail with any patch installation

== Installed Framework 3.5 Successfully after that

== So downloaded 3.5 SP1 Redistributable again and installed it successfully

Error:

Package 'Microsoft.VisualStudio.Xaml' has failed to load properly ( GUID = {E58C2A8B-BCC4-4559-AD59-D62EB6D58A22} ). Please contact package vendor for assistance. Application restart is recommended, due to possible environment corruption. Would you like to disable loading this package in the future? You may use 'devenv /resetskippkgs' to re-enable package loading.

== Tried devenv /resetskippkgs

== Collected the log devenv /log
== Logs created at %USERPROFILE%\Application Data\Microsoft\Visual Studio\8.0\ActivityLog.xml
== In that I did not find any failure
== So concluded that the packages are loading fine

== Tried repairing the Visual Studio 2008 but that will not help, best possible way is to install Visual Studio 2008 Service Pack 1

These issue can be always fixed with the installation of Visual Studio 2008 SP1

Download Visual Studio 2008 Service Pack Here

Framework Installation Log Snippet:

[02/05/09,12:55:54] XPSEPSC Installer: [2] Error code 1603 for this component means "Fatal error during installation.
"
[02/05/09,12:55:54] XPSEPSC Installer: [2] Setup Failed on component XPSEPSC Installer
[02/09/09,11:13:20] XPSEPSC Installer: [2] Error code 1603 for this component means "Fatal error during installation.
"
[02/09/09,11:13:20] XPSEPSC Installer: [2] Setup Failed on component XPSEPSC Installer
[02/09/09,11:13:21] WapUI: [2] DepCheck indicates XPSEPSC Installer is not installed.
[02/09/09,11:18:01] XPSEPSC Installer: [2] Error code 1603 for this component means "Fatal error during installation.
"
[02/09/09,11:18:01] XPSEPSC Installer: [2] Setup Failed on component XPSEPSC Installer
[02/09/09,11:18:01] WapUI: [2] DepCheck indicates XPSEPSC Installer is not installed.
[02/09/09,11:31:08] XPSEPSC Installer: [2] Error code 1603 for this component means "Fatal error during installation.
"
[02/09/09,11:31:08] XPSEPSC Installer: [2] Setup Failed on component XPSEPSC Installer
[02/09/09,11:31:08] WapUI: [2] DepCheck indicates XPSEPSC Installer is not installed.
[02/09/09,12:28:49] XPSEPSC Installer: [2] Error code 1603 for this component means "Fatal error during installation.
"
[02/09/09,12:28:49] XPSEPSC Installer: [2] Setup Failed on component XPSEPSC Installer
[02/09/09,12:28:50] WapUI: [2] DepCheck indicates XPSEPSC Installer is not installed.
[02/09/09,13:00:27] XPSEPSC Installer: [2] Error code 1603 for this component means "Fatal error during installation.
"
[02/09/09,13:00:27] XPSEPSC Installer: [2] Setup Failed on component XPSEPSC Installer
[02/09/09,13:00:27] WapUI: [2] DepCheck indicates XPSEPSC Installer is not installed.

dd_XPS Log Snippet:

0.015: 2009/02/09 18:40:41.985 (local)

0.015: c:\4070abb43da3a79374\update\update.exe (version 6.3.13.0)

0.015: Failed To Enable SE_BACKUP_PRIVILEGE

0.015:  Setup encountered an error:  You do not have permission to update Windows Server 2003.

Please contact your system administrator.

0.015: You do not have permission to update Windows Server 2003.

Please contact your system administrator.

0.015: Update.exe extended error code = 0xf004

0.015: Update.exe return code was masked to 0x643 for MSI custom action compliance.

Root Cause of the issue: You must have this user right to perform backup operations. Rights needs to be given to SE_SECURITY_PRIVILEGE

== The article http://support.microsoft.com/kb/888791 describes why these set of permission is required and one can always refer to the same

== The article is all about “The user rights that are required by Update.exe”

Resolution: Enable SE_SECURITY_PRIVILEGE

== To enable the rights we can use the command line “ntrights.exe +r SeBackupPrivilege -u machinename\Username”

I was able to this issue in one of the Windows 2003 R2 Box. Again it might vary in different OS.

Operating System: Windows XP Media Center SP2

Trying to install Visual Studio 2005 and it fails at the point where Document Explorer tries to get install

Log Says:

MSI (s) (20:E4) [14:44:06:031]: Assembly Error:Version %d.%d is not a compatible version.
MSI (s) (20:E4) [14:44:06:031]: Note: 1: 1935 2:  3: 0x80131107 4: IStream 5: Commit 6: 
MSI (s) (20:A8) [14:44:06:031]: Note: 1: 1304 2: microsoft.visualstudio.commonide.dll
MSI (s) (20:A8) [14:44:06:046]: Product: Microsoft Document Explorer 2005 -- Error 1304.Error writing to file: microsoft.visualstudio.commonide.dll.  Verify that you have access to that directory.

Error 1304.Error writing to file: microsoft.visualstudio.commonide.dll.  Verify that you have access to that directory.
MSI (s) (20:A8) [14:44:06:046]: User policy value 'DisableRollback' is 0
MSI (s) (20:A8) [14:44:06:046]: Machine policy value 'DisableRollback' is 0
Action ended 14:44:06: InstallFinalize. Return value 3.

Tried the Below Steps it did not worked

== Clean the GAC_MSIL and GAC_32 folder again
== Clean the NativeImage*2.0* folder inside %windir%\assembly
== Reboot the machine
== Use regedit to search for "Microsoft.VisualStudio.Editors" and rename any key you found
== Browse for the file dotnetfx.exe (in \wcu\dotnetframework) and double click the file to choose repair
== Run VS setup again

THE ISSUE GOT RESOLVED BY FOLLOWING THE BELOW STEPS

== Remove Framework 2.0 from Add/Remove
== Used the Framework cleanup Tool to remove Framework 2.0
== Found few entries of Visual Studio in Assembly GAC
== Most of them was not registered
== It was not giving the option for uninstall
== Tried manually deleting the entries
== That also did not help
== Hence decided to rename the Assembly folder
== This worked

The issue was with the Assembly as per the the MSI Log

MSI (s) (20:E4) [14:44:06:031]: Assembly Error:Version %d.%d is not a compatible version

== So once the Assembly was renamed the Visual Studio 2005 installation went successfully

The issue is usually caused due to Models that have Sonic Solutions Drive Letter Access (DLA) installed

Resolution

Try the following steps to install the software.

1. Start -> Run -> type MSCONFIG.

2. Check the Startup tab.

3. Look for an entry with Sonic Solutions Drive Letter Access Or "dlactrlw.exe".

4. Remove the check mark and click on OK.

5. Restart the computer.

6. Now you can use the DVD again to install the Visual Studio 2008 software.

6. To enable the DLA Follow the steps 1 to 5 again, check the entry this time

For Example it worked several times in these kind of scenarios :

Complain:

This is very strange. I received the Visual Studio 2008 DVD this morning and the exact same conditions occurred when IT tried to install the software. The CPU usage goes to 100% and the computer freezes.

I had the IT tech reboot and we checked the install requirements to be sure and as you can see below, this should install without issue. Also, be aware that the DVD player reads the Flash CS4 DVD without a problem. In fact, we installed the SQL Server Developer from the other DVD that accompanies Visual Studio 2008 without a hitch

Administrative Deployment Readme

Sometimes you might face issue if the files needed for the Administrative Installation Point are not extracted correctly.

The Below steps can be followed if the files are not extracted correctly:

In order to create Visual Studio 2008 Admin Install Point and deploying it follow the steps given below:

1. Create a folder called VS2008 in C drive.

2. Copy the contents of the VS folder from the DVD to this folder.

3. Download the full package version of the .Net Framework 3.5 from the following link.

.Net Framework 3.5 Redistributable

4. The file must be saved in the root of WCU\dotNetFramework folder.

Copy the following script and save it as a .BAT file in the VS2008 folder. The .BAT file should not go into the WCU folder. The script will fail.

Script to copy and save as .BAT file:

== Script Begins

set WORKFOLDER=C:\deployment
set dotNetFX35build=%WORKFOLDER%\dotnetfx35.exe
echo Creating Admin Install points for NETFX3 %PROCESSOR_ARCHITECTURE%
REM Create folders where work will be done
md %WORKFOLDER%\ext
md %WORKFOLDER%\VisualStudio2008\dotNetFramework
md %WORKFOLDER%\logs
REM pushd %WORKFOLDER%

REM ------------ File Extraction Section ------------

REM ## 64 Pre Requisites ##

REM Extract files for 64bitPrereq IA64
call .\WCU\64bitPrereq\IA64\vs_bsln.exe /q /X:%WORKFOLDER%\ext\64bitPrereqIA64

REM Extract files for 64bitPrereq X64
call .\WCU\64bitPrereq\x64\vs_bsln.exe /q /X:%WORKFOLDER%\ext\64bitPrereqx64

REM ## ARM > Device Emulator ##

REM Extract the files for Device Emulator
call .\wcu\arm\vs_emulator.exe /q /x:%WORKFOLDER%\ext\vs_emulator86

REM Extract the files for Device Emulator
call .\wcu\arm\vs_emulator_x64_vista.exe /q /x:%WORKFOLDER%\ext\vs_emulator64

REM ## Crystal reports does not need extraction ##

REM ## Document Explorer ##

REM Extract the files for Document Explorer
call .\wcu\DExplore\DExplore.exe /q /x:%WORKFOLDER%\ext\dexplorer\

REM ## Dot Net framework 3.5 ##

REM << The files in the folder cannot
REM be used download the full pack from
REM the MS site and save it in this location. >>

REM Extract the files from the NETFX35 redist SFX
call .\WCU\dotNetFramework\dotnetfx35.exe /q /x:%WORKFOLDER%\ext

REM ## Windows installer 3.1 has to installed separately by the user. ##

REM ## .NET Compact Framework and .Net Compact Framework v3.5 does not need extraction ##

REM ## Profiler ##

REM Extract files for Microsoft Visual Studio 2008 Performance Collection Tools X86
call .\wcu\Profiler\PerfCollectionTools_x86.exe /q /x:%WORKFOLDER%\ext\vs_profiler86

REM Extract files for Microsoft Visual Studio 2008 Performance Collection Tools X64
call .\wcu\Profiler\PerfCollectionTools_x64.exe /q /x:%WORKFOLDER%\ext\vs_profiler64

REM ## SQL is not extracted or installed by this script ##

REM ## VS Tools for Office ##

REM Extract the files for Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System Runtime
call ".\wcu\VS Tools for Office\vstor.exe" /q /x:%WORKFOLDER%\ext\vstor\

REM Extract the files for Microsoft Visual Studio Tools for the Microsoft Office system (version 3.0 Runtime)
call ".\wcu\VS Tools for Office\vstor30.exe" /q /x:%WORKFOLDER%\ext\vstor30\

REM ## WebDesignerCore ##

REM Extract files for Microsoft Web Designer Tools
call .\WCU\WebDesignerCore\WebDesignerCore.EXE /q /x:%WORKFOLDER%\VisualStudio2008\WDCore

REM ## WindowsMobileSDK does not need extraction ##

REM ## WinSDK ##

REM Extract files for Microsoft Windows SDK for Visual Studio 2008 Headers and Libraries
call .\WCU\WinSDK\WinSDK_Build.exe /Q /x:%WORKFOLDER%\ext\WinSDK_Build

REM Extract files for Microsoft Windows SDK for Visual Studio 2008 .NET Framework Tools
call .\WCU\WinSDK\WinSDK_NetFxTools.exe /Q /x:%WORKFOLDER%\ext\WinSDK_NetFxTools

REM Extract files for Microsoft Windows SDK for Visual Studio 2008 SDK Reference Assemblies and IntelliSense
call .\WCU\WinSDK\WinSDK_RefInt.exe /Q /x:%WORKFOLDER%\ext\WinSDK_RefInt

REM Extract files for Microsoft Windows SDK for Visual Studio 2008 Tools
call .\WCU\WinSDK\WinSDK_Tools.exe /Q /x:%WORKFOLDER%\ext\WinSDK_Tools

REM Extract files for Microsoft Windows SDK for Visual Studio 2008 Win32 Tools
call .\WCU\WinSDK\WinSDK_W32Tools.exe /Q /x:%WORKFOLDER%\ext\WinSDK_W32Tools

REM      ## END of extraction ##
REM
REM
REM
REM ------------ MSI File Extraction Admin Install Point ------------
REM
REM
REM ------------ MSI File Extraction Admin Install Point ------------
REM
REM
REM ------------ MSI File Extraction Admin Install Point ------------
REM
REM

REM ## 64 Pre Requisites ##

REM Admin point for 64bitPrereq IA64
call msiexec /qb /a %WORKFOLDER%\ext\64bitPrereqIA64\vs_bsln.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\64bitPrereqIA64

REM Admin point for 64bitPrereq X64
call msiexec /qb /a %WORKFOLDER%\ext\64bitPrereqx64\vs_bsln.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\64bitPrereqx64

REM ## ARM > Device Emulator ##

REM Admin point for Device Emulator x86
call msiexec /qb /a %WORKFOLDER%\ext\vs_emulator86\sde_vsd.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\vs_emulator86

REM Admin Pont for Device Emulator x64
call msiexec /qb /a %WORKFOLDER%\ext\vs_emulator64\sde_vsd64.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\vs_emulator64

REM ## Crystal reports ##

REM Admin point for Crystal Reports 2007
call msiexec /qb /a "WCU\Crystal Reports\CrystalReports2007.msi" TARGETDIR=%WORKFOLDER%\VisualStudio2008\Crystal_Reports

REM Admin Pont for Crystal Reports 2007 X64
call msiexec /qb /a "WCU\Crystal Reports\CRRedist2007_x64.msi" TARGETDIR=%WORKFOLDER%\VisualStudio2008\Crystal_Reports

REM ## Document Explorer ##

REM Admin Point for Document Explorer
call msiexec /qb /a %WORKFOLDER%\ext\dexplorer\hh_dex.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\dexplorer

REM ## Dotnet framework 3.5 ##

REM create the MSXML6 x86 admin install point
md %WORKFOLDER%\VisualStudio2008\dotNetFramework\MSXML6_x86
call msiexec /a %WORKFOLDER%\ext\wcu\dotNetFramework\dotNetFX30\x86\msxml6.msi /qb /l*v %WORKFOLDER%\logs\MSXML6_x86.log Targetdir=%WORKFOLDER%\VisualStudio2008\dotNetFramework\MSXML6_x86

REM create the MSXML6 x64 admin install point
md %WORKFOLDER%\VisualStudio2008\dotNetFramework\MSXML6_x64
call msiexec /a %WORKFOLDER%\ext\wcu\dotNetFramework\dotNetFX30\x64\msxml6.msi /qb /l*v %WORKFOLDER%\logs\MSXML6_x64.log Targetdir=%WORKFOLDER%\VisualStudio2008\dotNetFramework\MSXML6_x64

REM ------------------------------------------------------------
REM create the RGBRAST x86 admin install point
md %WORKFOLDER%\VisualStudio2008\dotNetFramework\RGBRAST_x86
call msiexec /a %WORKFOLDER%\ext\wcu\dotNetFramework\dotNetFX30\RGB9RAST_x86.msi /qb /l*v %WORKFOLDER%\logs\RGBRAST_x86.log REBOOT=ReallySuppress Targetdir=%WORKFOLDER%\VisualStudio2008\dotNetFramework\RGBRAST_x86

REM create the RGBRAST x64 admin install point
md %WORKFOLDER%\VisualStudio2008\dotNetFramework\RGBRAST_x64
call msiexec /a %WORKFOLDER%\ext\wcu\dotNetFramework\dotNetFX30\RGB9RAST_x64.msi /qb /l*v %WORKFOLDER%\logs\RGBRAST_x64.log REBOOT=ReallySuppress Targetdir=%WORKFOLDER%\VisualStudio2008\dotNetFramework\RGBRAST_x64
REM ------------------------------------------------------------
REM Extract NETFX 35 x86 components
md %WORKFOLDER%\ext\netfx35_x86
call %WORKFOLDER%\ext\wcu\dotNetFramework\dotNetFX35\x86\netfx35_x86.exe /q /x: %WORKFOLDER%\ext\netfx35_x86

REM Extract NETFX 35 x64 components
md %WORKFOLDER%\ext\netfx35_x64
call %WORKFOLDER%\ext\wcu\dotNetFramework\dotNetFX35\x64\netfx35_x64.exe /q /x: %WORKFOLDER%\ext\netfx35_x64

REM ------------------------------------------------------------
REM create the NETFX35 x86 admin install point
md %WORKFOLDER%\VisualStudio2008\dotNetFramework\netfx35_x86
call msiexec /qb /a %WORKFOLDER%\ext\netfx35_x86\vs_setup.msi USING_EXUIH=1 REBOOT=ReallySuppress /l*v %WORKFOLDER%\logs\netfx35_x86.log TARGETDIR=%WORKFOLDER%\VisualStudio2008\dotNetFramework\netfx35_x86
REM create the NETFX35 x64 admin install point
md %WORKFOLDER%\VisualStudio2008\dotNetFramework\netfx35_x64
call msiexec /qb /a %WORKFOLDER%\ext\netfx35_x64\vs_setup.msi USING_EXUIH=1 REBOOT=ReallySuppress /l*v %WORKFOLDER%\logs\netfx35_x64.log TARGETDIR=%WORKFOLDER%\VisualStudio2008\dotNetFramework\netfx35_x64

REM ------------------------------------------------------------
REM create the NETFX20 x86 SP1 admin install point

REM 2.0 SP1 files location
Set fx20=%WORKFOLDER%\ext\wcu\dotNetFramework\dotNetFX20\
md %WORKFOLDER%\VisualStudio2008\dotNetFramework\NETFX20_x86
call msiexec /a %fx20%netfx20a_x86.msi USING_EXUIH=1 REBOOT=ReallySuppress /l*v %WORKFOLDER%\logs\netfx20_x86.log TARGETDIR=%WORKFOLDER%\VisualStudio2008\dotNetFramework\NETFX20_x86

call msiexec /p %fx20%ASPNET.msp;%fx20%CLR.msp;%fx20%CRT.msp;%fx20%NetFX_CA.msp;%fx20%NetFX_Core.msp;%fx20%NetFX_Other.msp;%fx20%PreXP.msp;%fx20%WinForms.msp;%fx20%DW.msp /a %WORKFOLDER%\VisualStudio2008\dotNetFramework\NETFX20_x86\netfx20a_X86.msi /qb /l*v %WORKFOLDER%\logs\netfx20_x86_patch.log

REM create the NETFX20 x64 SP1 admin install point
md %WORKFOLDER%\VisualStudio2008\dotNetFramework\NETFX20_x64
call msiexec /a %fx20%Netfx20a_x64.msi USING_EXUIH=1 REBOOT=ReallySuppress /l*v %WORKFOLDER%\logs\netfx20_x64.log TARGETDIR=%WORKFOLDER%\VisualStudio2008\dotNetFramework\NETFX20_x64

call msiexec /p %fx20%ASPNET_64.msp;%fx20%CLR_64.msp;%fx20%CRT_64.msp;%fx20%DW_64.msp;%fx20%NetFX_Core_64.msp;%fx20%NetFX_Other_64.msp;%fx20%WinForms_64.msp;%fx20%ASPNET.msp;%fx20%CLR.msp;%fx20%CRT.msp;%fx20%NetFX_CA.msp;%fx20%NetFX_Core.msp;%fx20%NetFX_Other.msp;%fx20%PreXP.msp;%fx20%WinForms.msp;%fx20%DW.msp /a %WORKFOLDER%\VisualStudio2008\dotNetFramework\NETFX20_x64\Netfx20a_X64.msi /qb /l*v %WORKFOLDER%\logs\netfx20_x64_patch.log

REM ------------------------------------------------------------
REM create the NETFX30 SP1 x86 admin install point

REM 3.0 SP1 files location
Set fx30=%WORKFOLDER%\ext\wcu\dotNetFramework\dotNetFX30\
md %WORKFOLDER%\VisualStudio2008\dotNetFramework\NETFX30_x86
call msiexec /a %fx30%netfx30a_x86.msi USING_EXUIH=1 REBOOT=ReallySuppress /l*v %WORKFOLDER%\logs\netfx30_x86.log TARGETDIR=%WORKFOLDER%\VisualStudio2008\dotNetFramework\NETFX30_x86

call msiexec /p %fx30%WCF.msp;%fx30%WCS.msp;%fx30%WF.msp;%fx30%WPF1.msp;%fx30%WPF2.msp;%fx30%WPF_Other.msp;%fx30%XPS.msp;%fx30%WF_32.msp;%fx30%WPF2_32.msp;%fx30%WPF_Other_32.msp /a %WORKFOLDER%\VisualStudio2008\dotNetFramework\NETFX30_x86\netfx30a_X86.msi /qb /l*v %WORKFOLDER%\logs\netfx30_x86_patch.log

REM create the NETFX30 SP1 x64 admin install point
md %WORKFOLDER%\VisualStudio2008\dotNetFramework\NETFX30_x64
call msiexec /a %fx30%netfx30a_x64.msi USING_EXUIH=1 REBOOT=ReallySuppress /l*v %WORKFOLDER%\logs\netfx30_x64.log TARGETDIR=%WORKFOLDER%\VisualStudio2008\dotNetFramework\NETFX30_x64

call msiexec /p %fx30%WCF.msp;%fx30%WCS.msp;%fx30%WF.msp;%fx30%WPF1.msp;%fx30%WPF2.msp;%fx30%WPF_Other.msp;%fx30%XPS.msp;%fx30%WCF_64.msp;%fx30%WCS_64.msp;%fx30%WF_64.msp;%fx30%WPF1_64.msp;%fx30%WPF2_64.msp;%fx30%WPF_Other_64.msp /a %WORKFOLDER%\VisualStudio2008\dotNetFramework\NETFX30_x64\netfx30a_X64.msi /qb /l*v %WORKFOLDER%\logs\netfx30_x64_patch.log

REM ## Dotnet compact framework ##

REM Admin Point for .net compact framework 2.0
call msiexec /qb /a "WCU\NetCF\NetCFSetupv2.msi" TARGETDIR=%WORKFOLDER%\VisualStudio2008\NetCFSetupv2

REM Admin Point for .net compact framework 3.5
call msiexec /qb /a "WCU\NetCF\NetCFSetupv35.msi" TARGETDIR=%WORKFOLDER%\VisualStudio2008\NetCFSetupv35

REM ## Profiler ##

REM Admin Point for Microsoft Visual Studio 2008 Performance Collection Tools X86
call msiexec /qb /a %WORKFOLDER%\ext\vs_profiler86\dynamicanalysis_collectionbits.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\vs_profiler86

REM Admin Point for Microsoft Visual Studio 2008 Performance Collection Tools X64
call msiexec /qb /a %WORKFOLDER%\ext\vs_profiler64\dynamicanalysis_collectionbits.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\vs_profiler64

REM ## VS Tools for Office ##

REM Extract the files for Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System Runtime
call msiexec /qb /a %WORKFOLDER%\ext\vstor\vsto.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\vsto

REM Extract the files for Microsoft Visual Studio Tools for the Microsoft Office system (version 3.0 Runtime)
call msiexec /qb /a %WORKFOLDER%\ext\vstor30\trin_trir.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\vsto30

REM ## WebDesignerCore ##

REM Admin point for Microsoft Web Designer Tools
REM Special instruction to do this in the document.

REM ## WindowsMobileSDK ##

REM Admin point for WindowsMobileSDK
call msiexec /qb /a "WCU\WindowsMobileSDK\MagOrcasPPC.msi" TARGETDIR=%WORKFOLDER%\VisualStudio2008\WindowsMobileSDK
call msiexec /qb /a "WCU\WindowsMobileSDK\MagOrcasSP.msi" TARGETDIR=%WORKFOLDER%\VisualStudio2008\WindowsMobileSDK

REM ## WinSDK ##

REM Admin Point for Microsoft Windows SDK for Visual Studio 2008 Headers and Libraries
call msiexec /qb /a %WORKFOLDER%\ext\WinSDK_Build\VistaClientHeadersLibs-x86.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\WinSDK_Build86
call msiexec /qb /a %WORKFOLDER%\ext\WinSDK_Build\VistaClientHeadersLibs-x64.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\WinSDK_Build64

REM Admin Point for Microsoft Windows SDK for Visual Studio 2008 .NET Framework Tools
call msiexec /qb /a %WORKFOLDER%\ext\WinSDK_NetFxTools\WinSDK_nfxtoolsm_x86.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\WinSDK_NetFxTools86
call msiexec /qb /a %WORKFOLDER%\ext\WinSDK_NetFxTools\WinSDK_nfxtoolsm_amd64.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\WinSDK_NetFxTools64

REM Admin Point for Microsoft Windows SDK for Visual Studio 2008 SDK Reference Assemblies and IntelliSense
call msiexec /qb /a %WORKFOLDER%\ext\WinSDK_RefInt\winsdkintellisenserefassys-x86.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\WinSDK_RefInt86
call msiexec /qb /a %WORKFOLDER%\ext\WinSDK_RefInt\winsdkintellisenserefassys-amd64.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\WinSDK_RefInt64

REM Admin Point for Microsoft Windows SDK for Visual Studio 2008 Tools
call msiexec /qb /a %WORKFOLDER%\ext\WinSDK_Tools\VistaClientSDKTools-x86.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\WinSDK_Tools86
call msiexec /qb /a %WORKFOLDER%\ext\WinSDK_Tools\VistaClientSDKTools-x64.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\WinSDK_Tools64

REM Admin Point for Microsoft Windows SDK for Visual Studio 2008 Win32 Tools
call msiexec /qb /a %WORKFOLDER%\ext\WinSDK_W32Tools\VistaClientWin32Tools-x86.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\WinSDK_W32Tools86
call msiexec /qb /a %WORKFOLDER%\ext\WinSDK_W32Tools\VistaClientWin32Tools-x64.msi TARGETDIR=%WORKFOLDER%\VisualStudio2008\WinSDK_W32Tools64

== End Of Script

Note: The Script takes 10 to 15 minutes to extract all the components and create the admin points

Follow the next steps to create the admin point for Visual Studio 2008.

1. Click on Start>run type CMD, hit ok.

2. Change directory to VS2008 and run the following commands.

setup\setup.exe /CreateTransform C:\deployment\VisualStudio2008\VSMain\vs_transform.mst

3. Follow the on screen steps to create the transform.

4. To run the next command we need the product key. The key is in the setup\setup.sdb file.

NOTE: Retail media product key can only be located at jewel case or DVD cover.

5. Open the file with Notepad and search for "Product Key"

6. In the command window type the following command to apply the transform.

msiexec /a vs_setup.msi TRANSFORMS=C:\deployment\VisualStudio2008\VSMain\vs_transform.mst PIDKEY=<KEY> TARGETDIR=C:\deployment\VisualStudio2008\VSMain\

The process of creating the admin installation point is over now. Follow the steps below to Deploy it in AD.

Add a setup package to an Active Directory Group Policy

1. From the Start menu, choose Programs and then choose Administrative Tools.
2. Choose Component Services and then expand Active Directory Users and Computers. The Active Directory Users and Computers tree is displayed.
3. Right-click the Domain node and then choose Properties.
4. In the Properties dialog box, choose the Group Policy tab and then click Edit.
5. If you intend to set policies that apply to computers regardless of who logs on to them, expand Computer Configuration\Software Settings.

Note: Ensure that you map to the shared location on the Active Directory server; otherwise, it will not let you create a package for installation.

6. Right-click Software installation, choose New and then choose Package.
7. In the Open dialog box, browse to the location where you copied the deployment folder, and select the .msi file.
8. In the Deploy Software dialog box, choose Assigned and then click OK. (See the different Step for vs_setup.msi below)
9. Choose Auto Install to install the software automatically on every computer in the domain.
10. Click OK and then exit the Active Directory Users and Computers console.

Steps which needs to be followed for vs_setup.msi:

1. Select the .msi as described, click OK.

2. On Deploy software dialog choose Advanced, click OK.

3. On the next tabbed dialog select the Modifications tab.

4. Click on Add.. button and select the vs_transform.mst transform file that was created before.

Click ok to close the dialog box.

It should be ready for deployment now. Only thing just restart the client machines in order to complete the installation.

In couple of instances we have seen that after installing Visual Studio 2008 Beta, installing the RTM fails. There is no specific error but it is found that if it detects the Beta Components the installation fails.

In order to remove the Visual Studio 2008 Beta ( RTM Also ) the steps listed can be followed:

1. First make sure you remove Visual Studio 2008 from the Control Panel (Add/Remove Programs)

2. Make sure to remove the few more components which will be there at Add/Remove in case they are not removed after uninstalling Visual Studio 2008

a. Visual Studio 2008 Team Explorer

b. Microsoft Visual Studio Web Authoring Components

c. Microsoft Windows SDK for Visual Studio 2008 .Netframework Tools

d. Microsoft Windows SDK for Visual Studio 2008 Headers and Libraries

e. Microsoft Windows SDK for Visual Studio 2008 SDK Reference Assemblies and Intellisense

f. Microsoft Windows SDK for Visual Studio 2008 Tools

g. Microsoft Windows SDK for Visual Studio 2008 Win32 Tools

h. MSDN Library for Visual Studio 2008 – ENU

3. Delete the Folder C:\Program Files\Microsoft Visual Studio 9.0

4. Delete the Registry Key Below:

a. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\ Delete 9.0

b. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VSWCU\ Delete Microsoft Visual Studio Team System 2008 Team Suite – ENU

c. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VSA\ Delete 9.0

d. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\vsto runtime Setup\ Delete v9.0.21022

( In case you are not able to find any particular key you can ignore the same )

5. Once the above steps performed, with this E Mail you will find a attachment name MSIZAP. I am renaming it to .TXT

6. Save the file to “C” Drive and then rename it to msizap.exe ( You can install Windows Installer cleanup utility available in my download list and browse to the location C:\Program Files\Windows Installer Clean Up )

7. Open command prompt and make sure you are in the root drive C:\

8. Type msizap tw {80C06CCD-7D07-3DB6-86CD-B57B3F0614D8} ( Make sure you do not remove the bracket )

9. The MSI ZAP will make sure to remove if any components are left

10. Once these are done Restart the computer

11. This will make sure to remove the Visual Studio 2008 from the computer

This above steps should help removing the Visual Studio 2008 Beta from the machine and also if a situation comes where complete removal of Visual Studio 2008 is required the above steps can be followed.

While installing Service Pack 1 for Visual Studio 2008 Team Test Load Controller ENU its failing with the below error message in the Install Log:

Log Snippet:

MSI (s) (D8:88) [10:49:01:243]: Transforming table Binary.

MSI (s) (D8:88) [10:49:01:243]: Note: 1: 2262 2: Binary 3: -2147287038

MSI (s) (D8:00) [10:49:01:259]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSIAF.tmp, Entrypoint: GetSQLInstanceId

MSI (s) (D8:28) [10:49:01:259]: Generating random cookie.

MSI (s) (D8:28) [10:49:01:259]: Created Custom Action Server with PID 1916 (0x77C).

MSI (s) (D8:4C) [10:49:01:275]: Running as a service.

MSI (s) (D8:4C) [10:49:01:275]: Hello, I'm your 32bit Impersonated custom action server.

Action start 10:49:01: CA_GetSQLInstanceId.

MSI (s) (D8:88) [10:49:01:681]: Transforming table InstallExecuteSequence.

MSI (s) (D8:88) [10:49:01:681]: Transforming table InstallExecuteSequence.

MSI (s) (D8:88) [10:49:01:681]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038

Action ended 10:49:01: CA_GetSQLInstanceId. Return value 3.

Action ended 10:49:01: INSTALL. Return value 3.

Property(S): DiskPrompt = [1]

Property(S): UpgradeCode = {9E906A11-9706-373E-ADE9-693555097942}

Property(S): SystemFolder = C:\WINDOWS\SysWOW64\

Property(S): WindowsFolder_x86.3643236F_FC70_11D3_A536_0090278A1BB8 = C:\WINDOWS\

Property(S): SystemFolder_x86.3643236F_FC70_11D3_A536_0090278A1BB8 = C:\WINDOWS\SysWOW64\

Property(S): VersionNT = 502

Event Viewer:

EventType spinstaller, P1 microsoft visual studio 2008 sp1, P2 i, P3 1603, P4 dte90sp1-kb950425-enu.msp, P5 e, P6 9.0.30703.1, P7 1, P8 9.0.30729 1033, P9 x64_win2k3r2, P10 0.

Product: Microsoft Visual Studio 2008 Team Test Load Controller- ENU - Update 'KB950425' could not be installed. Error code 1603. Additional information is available in the log file C:\DOCUME~1\SayalaSu\LOCALS~1\Temp\Microsoft Visual Studio 2008 SP1_20080926_110206020-Microsoft Visual Studio 2008 Team Test Load Controller- ENU-MSP0.txt.

Screen Shots:

Root Cause Identified:

2.1.6 SQLPubWiz 1.2 fails to be installed on Visual Studio 2008 SP1

SQL Publishing Wizard cannot be installed in Visual Studio side-by-side installations.
SQL Publishing Wizard installation fails when you try to install a version of Visual Studio 2008 or Visual Web Developer Express 2008 on a computer where the service pack of these products is already installed. This is because Visual Studio 2008 SP1 installs a later version of SQL Publishing Wizard than the one that is included in Visual Studio 2008 or Visual Web Developer Express 2008, and SQL Publishing Wizard will not be installed if a later version is detected.

Existing scenarios include:
Attempting to install Visual Studio 2008 English on a computer that has Visual Web Developer SP1 English already installed. Attempting to install Visual Studio 2008 Japanese on a computer that has Visual Studio 2008 SP1 English or Visual Web Developer SP1 English already installed. The Setup program will finish and display this error message: "The following component failed to install: Microsoft SQL Publishing Wizard." However, both products will work with no loss of functionality.

Resolution:

Uninstall SQL Web Developer Web Edition from control panel and then try installing the service pack 1 for Visual Studio 2008.

While trying to install Visual Studio 2005 one of my client was getting error "Installing to mapped drive is not supported"

Complete Error

At least one component has an install path set to a mapped drive. Installing to mapped drive is not supported

Cause: This issue is seen when the C:\Program Files\Common Files location in the registry is set to a Mapped or a Share Drive

Resolution: Registry Edit is require for this

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

The registry key to modify is:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion

CommonFilesDir: This key should point to C:\Program Files\Common Files

Today when I was working with one of my client, I came across this situation. I tried stopping the Anti Virus Services but nothing helped.

Then I thought of deleting the Temporary Folder by going to Start > Run > %Temp% > Ok . I was not able to delete the temporary files there in that folder

Then I decided to recreate the Temp Folder, Follow the below instruction:

Operating System: Windows Vista

1. Right Click My Computers

2. Click Properties

3. Click Advance System Settings

4. Go to Advance Tab and Click Environment Variables

5. Select Temp > Edit and Copy %USERPROFILE%\AppData\Local\Temp

6. Click Ok and Exit the Screen

7. Suggestion to Restart the Computer

8. Go to Environment Variables again following 1 to 4 Steps

9. Select Temp > Edit and Paste %USERPROFILE%\AppData\Local\Temp

10. Click OK and Exit

11. Now try using Visual Studio 2008 it will install

This above steps I mentioned from one of the scenario and it might be different in some cases, In case of such issues feel free to get back to me at any point of time.