Error Loading TransformXml

To check the beginning of the Sln file, you can either open it in VS2013 and select the solution root node in the solution explorer, then go to File > Save .sln, or refer to the solution found in this link regarding the error message “TransformXml task could not be loaded from Microsoft.Web.Publishing.Tasks.dll.” It’s worth noting that while I had VS 2012 installed on an E: drive, it was not affected by this issue and served as my backup option. Hope this helps.

Question:

My previous solution functioned effectively with VS 2012, but now I am relocating it to VS 2013.

Upon attempting to construct a setup that entails the replacement of web.config, an error surfaces.

An error occurred while trying to perform an action on ”
transformxml

task could not be loaded
from the assembly located at C:Program Files (x86)MSBuildMicrosoftVisualStudiov11.0WebMicrosoft.Web.Publishing.Tasks.dll. The system is unable to locate the file specified as
load file
or
assembly ‘file
:///C:Program Files (x86)MSBuildMicrosoftVisualStudiov11.0WebMicrosoft.Web.Publishing.Tasks.dll’ or any of its dependencies. To resolve this issue, ensure that the declaration is accurate, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.

Essentially, my

v11.0

lacks build tools, which is expected since I utilize
Visual Studio
2013. The build tools are instead located in a designated folder called

v12.0

. While I could easily move the build tools to their appropriate location, I am in search for a more permanent solution.

Upon inspecting my .csproj file, I came across the following configuration.


    10.0
    $(MSBuildExtensionsPath32)MicrosoftVisualStudiov$(VisualStudioVersion)

Despite my attempts to modify it, I am still unclear about why v11.0 is possible. Explicitly setting
visualstudioversion
did not have any effect.

I am wondering about the origin of these paths and their configuration.


Solution:

MS has been avoiding upgrading
sln file
unnecessarily since the release of vs2012 to ensure that solutions can still be opened in the older version. If you have upgraded from vs2012 to vs2013, there is a possibility of opening solutions in vs2012, which has happened to me with several updated solutions.

Examine the start of the SLN file.

Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2013

or:

Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2012

To modify it using VS, launch vs2013 and choose the root node of the solution in the solution explorer. Finally, click on File and then Save .sln (Ctrl+S).

Frequently Asked Questions

Posted in Uncategorized