I'm trying to automatically add an entire folder structure to a VS C++ makefile project. This isn't to make the project build (it'll always build from the scons file), I mostly want to use VS to edit the code/find in projects/intellisense etc.
I've tried the solutions suggested here : Is there a way to automatically include content files into asp.net project file? My project currently includes the tags
<ItemGroup>
<Content Include="$([System.IO.Directory]::GetFiles('$(ProjectDir)..\', '*.cpp', SearchOption.AllDirectories))" />
<Content Include="R:\src\FabricEngine\FabricUI\**\*.*" />
</ItemGroup>
But I haven't had any success - none of the suggestions give me the list of files in Visual Studio. Is this an MSBuild feature that isn't supported by VS perhaps? Or is it limited to managed products? Any suggestions on how to get this working?
Got similar problem and found that used following worked for me:
<None Include="$([System.IO.Directory]::GetFiles('$(MSBuildProjectDirectory)', '*.cpp', SearchOption.AllDirectories))" />
But issue with this is it just takes really long time and crashes if you have lot of files
Related
I work on a dotnet project in rider. My colleague works on the same project and prefers visual studio. The project contains a lot of test fixtures (thousands). Rider tries to index all those files, which I don't need. So I exclude the test file folder from the index. What rider does is it adds one line per file in the excluded folder to the .csproj file:
<ItemGroup>
<Folder Include="excludedDir\subdir1\" />
<Folder Include="excludedDir\subdir2\" />
<_ContentIncludedByDefault Remove="excludedDir\file_0001.xml" />
...
<_ContentIncludedByDefault Remove="excludedDir\file_9999.xml" />
</ItemGroup>
That seems to solve the indexing problem for rider. But Visual Studio cannot handle a .csproj file that is 10'000 lines long. Just opening the project takes 5 minutes at best. So working on that project with that .csproj file is not an option anymore.
Has anyone ever had a similiar issue and found a solution to:
making VS ignore the _ContentIncludedByDefault keys
or excluding files from rider index without having rider specify each file individually?
I have a large solution in which the "root" project includes feature projects by glob:
<ProjectReference Include="..\Feature\*\*.csproj" />
This works, despite not looking great in the references list, but the issue that occasionally Visual Studio will rewrite the csproj with all of the project references resolved:
<ProjectReference Include="..\Feature\A\A.csproj" />
<ProjectReference Include="..\Feature\B\B.csproj" />
It's not clear what triggers this, but I'm guessing it might have something to do with NuGet.
Is there anyway to stop VS from doing this (akin to using DisableFastUpToDateCheck for custom MSBuild scenarios)?
It's not clear what triggers this, but I'm guessing it might have something to do with NuGet.
It should be related to the items in the ItemGroup. I have the similar issue before, but the difference is that I use wildcards to contain .cs files and your are .csproj files, looks like:
<ItemGroup>
<Compile Include="**\*.cs" />
</ItemGroup>
When I delete one of .cs file in the <ItemGroup>, the wildcard gets expanded in the csproj file. For you case, if I deleted the the C.csproj project from Visual Studio (Add it before, reload the root project), then I got the same result as you.
For this issue, many other community members submit a user voice to Visual Studio team: VS IDE should support file patterns in project files. Now this is well supported in the new project system used by .NET Core and .NET Standard in Visual Studio 2017, but they haven't done the work to support it for existing project types.
Is there anyway to stop VS from doing this (akin to using DisableFastUpToDateCheck for custom MSBuild scenarios)?
To resolve this issue, you can use option Exclude="..." to exclude the project that you do not want to refer to:
<ItemGroup>
<ProjectReference Include="..\Feature\*\*.csproj" Exclude="..\Feature\C\C.csproj" />
</ItemGroup>
Or, if you want to delete one of project and keep the wildcard pattern, you only need to unload the root project, then delete the reference project, reload the root project, the wildcard pattern would be preserved.
Hope this helps.
I've done further research on this.
For testing, you can consistency reproduce the expansion by renaming any project that's included in the wildcard pattern.
Also, the easiest way to prevent the expansion is to:
Move the project reference globs into Directory.Build.props or another external file
Set DisableFastUpToDateCheck to true in your csproj
Using properties doesn't work and isn't required, likewise with using an Exclude.
It would appear that Visual Studio does not publish .ts files by default but does publish the .map files when using Web Deploy. I found an article which says I should add the following to the .csproj file:
<Target Name="AddTsToContent" AfterTargets="CompileTypeScript" Condition="'$(BuildingProject)' != 'false'">
<ItemGroup>
<Content Include="#(TypeScriptCompile)" Condition="'$(Configuration)'=='Debug'"/>
</ItemGroup>
</Target>
This did in fact seem to work as immediately after adding this the .ts files did in fact publish. Unfortunately I had to immediately remove the setting because after adding this none of typescript project includes worked anymore and the project wouldn't compile because all of a sudden all the path for references were wrong.
/// <reference path="../../sharedlibv2/sharedlibv2/ts/fb.core.ts" />
needed to be
/// <reference path="../../../../sharedlibv2/sharedlibv2/ts/fb.core.ts" />
in order to reference correctly. This path is completely invalid as it goes backward beyond the root of my hard drive, so clearly something is messed up. There are many hundreds of shared project files affected here and the reference this setting seems to require is not going to fly with others using these projects. I am guessing but haven't proven it that there will be other problems show up anyway.
I am using Visual Studio 15.5.7. Is there any other method of getting Visual Studio to publish .ts files via Web Deploy ?
I have a solution with multiple web projects. And there is common tsconfig which is used to build all typescript in solution. Build is called via webpack, so I don't want any typescript support from visual studio. More precisely, I want some support — in navigating and refactoring, but I don't want VS to build this code.
So I removed all references to typescript targets from csproj and everything works fine. But any time I add a new typescript file, VS gladly says
Your project has been configured to support TypeScript
and returns all typescript targets back to csproj.
Can I prevent VS from doing it? Of course I can live with it, but removing garbage from csproj after each adding seems uncomfortable.
UPD: found post on uservoice of VS https://visualstudio.uservoice.com/forums/121579-visual-studio-ide/suggestions/13420095-ask-to-configure-projects-for-typescript. But maybe there is solution already available. Or you can like this uservoice if you agree that it is an annoying problem :)
Found solution on uservoice (https://visualstudio.uservoice.com/forums/121579-visual-studio-ide/suggestions/13420095-ask-to-configure-projects-for-typescript).
Seems a bit ugly but it works.
Steps to fix:
Add some ts file to project and let VS add some bullshit to your csproj
ctrl-shift-s to make sure csproj is updated
Open csproj in any text editor and then:
Find import of Microsoft.TypeScript.Default.props and replace it's Condition="..." to Condition="false"
Remove line with TypeScriptToolsVersion
Find import of Microsoft.TypeScript.targets and replace it's Condition="..." to Condition="false"
Now after adding file VS will stop trying to do smth with project. And typescript will not be compiled on save and build, so you need to use gulp/webpack/grunt/whatever.
Visual Studio 2019 (16)
Add to *.csproj file
<ItemGroup>
<None Remove="**/*.ts" />
<Content Remove="**/*.ts" />
<TypeScriptCompile Include="**/*.ts" />
</ItemGroup>
Solution is described here: https://developercommunity.visualstudio.com/t/vs-modifies-csproj-file-with-typescriptcompile-ite/288648
Is there any way (plugins / extensions are perfectly fine) to show ONLY items that are excluded from a project / solution?
I have a project in which I've just done some significant refactoring and several files and folders are no longer needed. Now I want to remove them from source control (Mercurial, VisualHG plugin is installed in VS2010). It's a rather large solution so I'd rather not have to manually drill through Solution Explorer to find them.
Or, if someone has another process to do this I'm certainly open to that as well.
Theres no existing addon at the moment. As the project files are XML (see below), in theory you could write an app to parse it and then compare it to the contents of the project directory; and enumerate each one gathering a list of items that are not included.
<ItemGroup>
<Content Include="rootFile.html" />
<Content Include="Directory1\File1.xml" />
<Content Include="Directory2\File2.xml" />
<ItemGroup>
As for integrating this behaviour into Visual Studio, either file a feature request with Microsoft or write this addon.