I had the same error. I solved it by following the procedure : Shutdown all instances of Visual Studio Delete %LocalAppData%\Microsoft\VisualStudio\15.0_f4938f75\privateregistry.bin file (the ID after 15.0_ may be different per machines) Start VS as normal user all credit for this should go to https://developercommunity.visualstudio.com/content/problem/31188/access-denied-error-1.html
I have the need to remove and rename a selection of solution/project configurations in Visual Studio. Is there a tool which will help with this? Short answer: No. Long answer: Sort-of (e.g., you’re going to integrate “helper” tools which are incomplete, and write custom scripting/work to create/integrate into your configuration management process). Editorial comment: Great … Read more
There is a plugin to Visual Studio 2010 that will prompt you drag & drop files in Solution Explorer: http://visualstudiogallery.msdn.microsoft.com/en-us/d491911d-97f3-4cf6-87b0-6a2882120acf
There are 2 parts of your question: How to configure solutions to build assemblies/EXE into folders of your choice – this is configured through properties of the project in VS (project properties -> build -> output path). Also value of check “copy local” property on each reference. How to load assemblies files from non-default locations … Read more
A PowerShell implementation that recursively scans the script directory for .csproj files and adds them to a (generated) All.sln: $scriptDirectory = (Get-Item $MyInvocation.MyCommand.Path).Directory.FullName $dteObj = [System.Activator]::CreateInstance([System.Type]::GetTypeFromProgId(“VisualStudio.DTE.12.0”)) $slnDir = “.\” $slnName = “All” $dteObj.Solution.Create($scriptDirectory, $slnName) (ls . -Recurse *.csproj) | % { $dteObj.Solution.AddFromFile($_.FullName, $false) } $dteObj.Solution.SaveAs( (Join-Path $scriptDirectory ‘All.sln’) ) $dteObj.Quit()
I think you need to investigate properties files, i.e. *.vsprops (older) or *.props (latest) You do need to add the properties file manually to each project, but once that’s done, you have multiple projects, but one .[vs]props file. If you change the properties, all projects inherit the new settings.
This problem preceeds NuGet. If you have a project referenced in two solutions, and change assembly references in the project when it is open in one solution, of course it will change the reference path for that project when it is open in the other solution. This has always been the case, regardless of how … Read more
Find All (CTRL+SHIFT+F) “Find what:” = Reference.*ReplaceThisTextWithProjectName Check “Use:” -> “Regular Expression” in the “Find options” section “Look at these file types:” = “*.*proj* ” “Look in:” = Select a directory/folder on your drive. Don’t use “Entire Solution” it won’t get to the project file itself. (Don’t forget to check “Include sub-folders”)
Change your compiler for C/C++/Objective-C: Xcode > Target > Build Settings > Build Options > Compiler for C/C++/Objective-C Select Default compiler (Apple LLVM x.y)
It worked for my just adding the it to the ProjectFolder, and also add the folder programmatically like this. var p = new Microsoft.Build.Evaluation.Project(@”C:\projects\BabDb\test\test.csproj”); p.AddItem(“Folder”, @”C:\projects\BabDb\test\test2″); p.AddItem(“Compile”, @”C:\projects\BabDb\test\test2\Class1.cs”); p.Save();