Difference between revisions of "VS 2010"
From Richard's Wiki
| Line 8: | Line 8: | ||
::Remove VS2010 to start from scratch. | ::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. | ::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. | ||
Revision as of 03:41, 24 August 2010
- 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.
