Difference between revisions of "VS 2010"
From Richard's Wiki
| Line 1: | Line 1: | ||
| + | * [http://www.mattgawarecki.com/2011/02/workaround-visual-studio-2010-setup-project-unable-to-update-dependencies/ WORKAROUND: Visual Studio 2010 Setup Project “Unable to update dependencies”] | ||
* [http://msdn.microsoft.com/en-us/library/cc442767.aspx Deploying an Office Solution by Using Windows Installer (VS2010, MSDN)] | * [http://msdn.microsoft.com/en-us/library/cc442767.aspx Deploying an Office Solution by Using Windows Installer (VS2010, MSDN)] | ||
* [http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/9e5f58e4-6320-41a9-b5fb-a2365f1025f9 Change VS2010 RTM Owner and User Details] | * [http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/9e5f58e4-6320-41a9-b5fb-a2365f1025f9 Change VS2010 RTM Owner and User Details] | ||
Latest revision as of 21:20, 5 October 2011
- WORKAROUND: Visual Studio 2010 Setup Project “Unable to update dependencies”
- Deploying an Office Solution by Using Windows Installer (VS2010, MSDN)
- Change VS2010 RTM Owner and User Details
- In Summary -
- Installer will automatically read the information like organization, user from the registry key.
- For organization, it seems to read the value of "RegisteredOrganization" key under "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion".
- For user, it seems to read the value of "RegisteredOwner"under "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion".
- Remove VS2010 to start from scratch.
- Then go to these two registry keys mentioned above and change the value as you want. After that, run the installer to setup VS2010 again.
- To run a powershell script as post-build:
- Add the postbuild.ps1 file from the sample project into the project root folder
- Open the project properties page and in the Build Events section put this in the “Post-build event command line” text box:
- PowerShell -command "set-executionpolicy -ExecutionPolicy bypass"
- PowerShell -command "$(ProjectDir)postbuild.ps1" '$(SolutionDir)' '$(ProjectDir)' '$(TargetDir)' '$(TargetFileName)' '$(ConfigurationName)'
- Note the huge security hole in setting execution policy system-wide.
- See localhost traffic in Fiddler when debugging VS2010 web project, easiest way is to use http://ipv4.fiddler to hit localhost on the IPv4 adapter, or use http://ipv6.fiddler to hit localhost on the IPv6 adapter. This works especially well with the Visual Studio test webserver (codename: Cassini) because the test server only listens on the IPv4 loopback adapter. Alternatively look at section "Why don't I see traffic sent to http://localhost or http://127.0.0.1?" in http://www.bayden.com/fiddler/help/hookup.asp
