A few days ago, I set up a Windows 10 by clean installation and then installed Visual Studio 2019 Community on it.
Now, I want to customize Microsoft.Cpp.Win32.user.props and Microsoft.Cpp.x64.user.props files to add additional include paths for all my VC++ projects.
But I can't find these files on my brand-new machine.
They should be located at %localappdata%\Microsoft\MSBuild\v4.0, but there is no MSBuild directory.
Does it mean that the installation of Visual Studio failed, or do I need some additional procedures to create default *.user.props files?
I've confirmed that the VC++ can build a simple hello-world project.
Edit: Attached a screenshot of the Property Manager. There is no user property sheet.
According to Microsoft, VS 2019 no longer creates the .props files by default.
From Cannot see Microsoft.Cpp.Win32.user in Property Manager:
The behavior is intended. Visual Studio 2019 will not create .user files anymore. But if .user files already exist, projects will automatically import them.
Related
I'm trying to create Setup project for my application in Visual Studio 2019 that needs Access Database Engine 2010/2016.
I tried following all the information that I could find on web but no success.
I created accessdatabaseegine folder under C:\Program Files (x86)\Microsoft SDKs\ClickOnce Bootstrapper\Packages and put appropriate Product.xml in it and Eula.rtf & Package.xml in en folder underneath accessdatabaseegine folder. I used Eula.rtf after trying license.txt which didn't work.
But in spite of doing this, MS Access Database Engine installation option would not show up in prerequisite menu on visual studio 2019 set up project. Tried with VS 2017 as well with no result.
Any suggestions and other application installer that may help achieve this.
Thanks,
I think if you put the customized bootstrapper folder into this path: C:\Program Files (x86)\Microsoft SDKs\ClickOnce Bootstrapper\Packages, then it should be listed here: right-click the Setup project > Properties > click Prerequisites… button and you will see it listed in Choose which prerequisites to install window.
I'm using Visual Studio 2015 update 3 with TFS hosted at visualstudio.com.
When I add a C# class file to one of my projects in Visual Studio, it's not automatically added to source control. For other projects in the same solution, C# class files are added automatically, as expected.
When I then add the file, manually, in the project with this problem, I get the following question;
I have to confirm to add the file to source control.
There is a similar question (Visual Studio 2015 new files not being added to source control automatically), associated with a "release" branch, which is not the case here (at least I think so - our TFS-project has never been branched)
We've never configured any .tfignore manually.
This started to happen recently and occurs on all development machines, so it's probably not a client machine issue.
I'm clueless, so any help is highly appreciated.
UPDATE
I've discovered that the problem occurs in projects with names ending with ".Lib"
Projects:
Core (ok)
Core.Lib (files not added automatically)
Communication (Ok)
Communication.Lib (files not added automatically)
I tried to add a test project Test.Lib to my solution. This project was not added to TFS either, but project Test was.
The "lib" extension is the problem. Try renaming the project folder to something else, eg. "CoreLib".
To reproduce this behavior / bug, try the following:
Create a Test directory in a directory controlled by TFS
Create a Test.Lib subdirectory in this directory.
Add a file, test.cs, to Test.Lib. (Test\Test.Lib\test.cs)
In Visual Studio's Source Control Explorer, try adding the new Test directory to source control. You'll see test.cs on the "Excluded items" tab.
The "lib" extension is used by binary files, and these are ignored by Team Explorer by default. I haven't found an official list of filetypes anywhere, but other affected file types are dll, exe, obj and possibly others. You can include these files manually by right-clicking them and selecting "Include".
It's possible to alter the way the VS debugger displays types even for types you don't own by altering autoexp.cs.
However, in my installation this file does not exist in My Documents/Visual Studio 2015/Visualizers/ nor in another folder. It does exist in the 2013 folder: My Documents/Visual Studio 2013/Visualizers/autoexp.cs
Did its location change? Has the functionality been (re)moved?
It is still possible to place visualizer dll's in this folder, the file just isn't there by default anymore.
I'm working on an installer that needs to add several files to AVR Studio 5, an IDE developed by Atmel that is based on the Visual Studio Isolated Shell. These files include project templates for the "New Project" dialog.
By experimenting, I found that I can successfully add the project templates and get them to show up in the dialog if I simply copy them into C:\Program Files (x86)\Atmel\AVR Studio 5.0\ProjectTemplates\ and then delete or rename C:\Program Files (x86)\Atmel\AVR Studio 5.0\ProjectTemplateCache\cache.bin. I have not been able to find any good documentation on how the Visual Studio ProjectTemplateCache folder works. It seems to contain the same files as the ProjectTemplates folder, plus the cache.bin file, so I'm not sure why it would be useful. After I rename cache.bin, Visual Studio does not regenerate it, which makes me worried that renaming it might have some permanent consequences. Is renaming cache.bin a bad idea? What problems can it cause?
Is there another, easy way to install new project templates? Ideally I would like something that is easier than creating a Visual Studio Extension (.vsix) file, as recommended in this previous StackOverflow question: Installing a custom project template with Visual Studio Installer project
The installer I am working on uses NSIS, if that matters.
For my isolated shell I copy my template .zip files to 'Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\ProjectTemplates' and '\ItemTemplates'. I then run my isolated shell with the command line '/installvstemplates'. This rebuilds the caches and when you next run the isolated shell, they show up properly.
I also had to target the isolated shell in my extension manifest files.
Have you tried any of these?
If per user project templates are fine, you can drop them in <My Documents>\AVRStudio\Templates\ProjectTemplates.
Today I have upgraded a VS 2008 project to VS 2010 simply by opening the solution file (right click -> open with -> Visual Studio 2010).
I have successfully built the project (debug and release configurations). When I run the project within Visual Studio I get the following weird error:
Notice that \.\? The actual path on my computer is C:\xxxxxx\Application\Debug
What is the cause of path being messed up? And how to fix it? Anyone knows?
BTW. The executable is in \Debug folder and runs fine if I click on it
EDIT
Language: C++ (MFC)
The Output Directory was hardcoded in VS2008 configuration properties to:
Output directory: .\Debug\.
Intermediate directory: .\Debug\tmp\.
If I change that to $(SolutionDir)$(Configuration)\ and $(Configuration)\ respectively the output folders are messed up completely: the \Debug folder is full with .sbr files and all the object files are located in \Debug\tmp after I build the solution. Even though when I build (after changing the output configurations) it says successfully built, but it can't find the .exe file
There are several third party libs but I don't see how that would affect it in any way.
[SOLVED]
VS 2010 apparently handles the project configurations differently than VS 2008. Having the output path hardcoded in the 2008 configurations caused confusions for 2010. I have replaced the hardcoded paths with VS defaults (using variables instead) and the problem was solved