-
Notifications
You must be signed in to change notification settings - Fork 20
Make it compatible with VS 2017 new .csproj format #1
Comments
Hi @golavr I just installed this extension and am using the latest .csproj format. However, when I use "Add Config Transforms" for a config file it corrupts my project file. Could you advise when this fix\enhancement will be available? |
Hi @patricknolan you need to remove old configurations from project file prior using the new version since i made some breaking changes in the format. Remove the following sections manually: |
Fixed in v3.2 |
Hi @golavr I just installed v3.2 and when I run "Add Config Transforms" for a config file the project still fails to load with the error
Should this be working with v3.2 when using the latest cproj file format in 2017? |
@patricknolan please send me sample of your project i want to look into it. Please also check if path of <UsingTask TaskName="TransformXml" AssemblyFile="..." in project file is correct. |
Hi @golavr sorry for the slow response. I have attached a sample project which is basically the ASPNet.Core template project. If I try and "Add Config Transforms" for the web.config it fails. Should this work? |
Hi @golavr just checking if you got my previous message? |
When used in a VS2017 .csproj (i.e. ), targets must be changed to follow the new syntax, and therefore be correctly executed.
before (will not be executed)
<Target Name="AfterCompile" ... >
<Target Name="AfterPublish" ... >
after (will be executed)
<Target Name="TransformConfig" AfterTargets="AfterCompile" ... >
<Target Name="CopyTransformedConfig" AfterTargets="AfterPublish" ... >
The new Target names above are just an exemple, it does not matter anymore AFAIK.
The text was updated successfully, but these errors were encountered: