will help you This is a bug in the VS 2008 SP1, and only in large and/or complex projects. This has reportedly been corrected in Visual Studio 2010 Beta 2 which from my testing appears to be correct. Because 2010 seems to be fixed with regard to this issue I doubt they will fix this in 2008.
Using windows environment variables as registry values in Visual Studio Installer
this will help The Windows registry supports this natively with the REG_EXPAND_SZ registry value type. Just use REG_EXPAND_SZ instead of REG_SZ when you want to embed environment variables in the registry key value.
var registry = Registry.CurrentUser.OpenSubKey("Environment");
var temp = registry.GetValue("TEMP") as string;
like below fixes the issue There is no way to do this with the current APIs in Visual Studio 2010. This is why we're building the Roslyn APIs so you could. When you install the CTP, we setup a Roslyn instance that replaces the standard language services with the Roslyn ones, and you can ask your question directly to it. If you don't want to be dependent upon running in the Roslyn instance (which I assume is the case), then it gets a bit trickier. You can invoke the parsers to understand you're on a call named MessageBox.Show, but to get the semantics you'd have build up a Compilation making sure you get all the project references and source files right. That's a far trickier proposition, so depending on your scenario you might want to "cheat" as much as possible.
Visual Studio: Assembly name and Default namespace from project name
I wish did fix the issue. Context: setting up the Assembly Name/Default namespace in the Project Properties (right click on project, Properties, Application tab; or edit the .csproj). , How can I get this done?
Can't change default language of an assembly in Visual Studio 2017