I recently upgraded to Visual Studio 2017. For my WCF-Web-Service projects I have different config files for different publish settings.
When I click on the "Preview Transform" entry in the context menu I get the error message:
The assembly '' containing the transform build task could not be found.
However, if I publish the Service, the transformation is applied.
The curious thing is, I have two development PCs. I upgraded to Vs2017 on both and I get this error on BOTH.
I found the solution. This seems to be a Bug in Visual Studio 17 v15.8.1. Upgrading to v15.8.2 resolves this issue:
https://learn.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes#15.8.2
Preview Transform gives error.
https://developercommunity.visualstudio.com/content/problem/310891/preview-transform-gives-error.html
Related
Good evening,
I have created a Web Form using Visual Studio 2022, and I have created a Web Setup project to help our customers to install the site on their server. I used the official extension that allows to create Setup projects in VS2022 (Microsoft Visual Studio Installer Projects); everything worked fine until some days ago, when VS2022 started to show the following error when trying to load the installer project:
"Unable to open project .../Setup.vdproj".
This is the error I am getting when I try to open/create a Web Setup project
I tried to open it also with VS2019, which I still had installed on my computer, but I got the same error.
At the beginning I thought it was an issue related to the project (maybe for some reasons some files had been corrrupted), so I tried to create a new Web Setup project, both on VS2022 and VS2019. Again, the same error appeared, on both versions of VS. At this point I tried to load the already existing project on another computer, and on the other computer everything worked perfectly, the project was loaded immediatly and no issues have been detected.
I tried to unistall and re-install the Microsoft Visual Studio Installer Projects extension, it didn't solve the problem; I tried to repair VS2022, it didn't solve the problem; I tried to completely uninstall VS2022 and VS2019 and re-install only VS2022, and guess what? It didn't solve the problem.
Does anyone know how to fix this problem, and what is the reason why I am unable to neither load nor create Web Setup projects?
Thank you,
Giacomo
I have created a vue.js project in Windows 10 Visual Studio 2019 from the project template "Basic Vue.js Web Application" using Javascript.
I went to publish the project, and I get the error below. I have seen various places in Google searches relating to the problem, but not a resolution.
Does anyone know if vue.js publish is working in Visual Studio 2019?
I tried adding a web.config from a blank node js project as suggested in https://developercommunity.visualstudio.com/content/problem/157870/cannot-publish-nodejs-web-project-to-file-location.html but I get the error below : -
Severity Code Description Project File Line Suppression State
Error Copying file .\node_modules\.cache\uglifyjs-webpack-plugin\content-v2\sha512\3f\9e\eeb908c1d3d1209cf989d88110e80db17761bafb59b6410526f7c88239a213e2b0213f0a0840201e75b12319b3fdcf3196ee1682a2feeab4d0d4314cb32a to obj\Release\AspnetCompileMerge\Source\.\node_modules\.cache\uglifyjs-webpack-plugin\content-v2\sha512\3f\9e\eeb908c1d3d1209cf989d88110e80db17761bafb59b6410526f7c88239a213e2b0213f0a0840201e75b12319b3fdcf3196ee1682a2feeab4d0d4314cb32a failed. Could not find a part of the path 'obj\Release\AspnetCompileMerge\Source\.\node_modules\.cache\uglifyjs-webpack-plugin\content-v2\sha512\3f\9e\eeb908c1d3d1209cf989d88110e80db17761bafb59b6410526f7c88239a213e2b0213f0a0840201e75b12319b3fdcf3196ee1682a2feeab4d0d4314cb32a'. VuejsApp01 C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VisualStudio\v16.0\Web\Transform\Microsoft.Web.Publishing.AspNetCompileMerge.targets 615
It is complaining (or seems to be) about uglifyjs-webpack-plugin ?
I recently used the repair function in my Visual Studio Installer that I thought could fix the error message: Microsoft data transformation services designer package did not load correctly. However it turns out there is a new error message when I wanted to load my previous project: The "Package" package did not load correctly.
If I continue the loading, I will receive some other warning message in the solution Explorer saying my project is "incompatible" and "the application is not installed":
I initially also tried to follow some online solution and tried to repair Microsoft SQL Server Data Tools in control panel. It doesn't allow me to repair and says Setup Failed almost immediately after I click on the repair button.
Initially I was trying to add an WCF extenion in Visual Studio but seemed failed and threw the first error message to me. Then when I try to repair, the first error message is gone and I was given the second error message. Now I stuck in there.
I have also checked if SSDT is included in the installer and New project types:
It seems the SSDT is selected in the Visual Studio Installer and all my current project types are listed in the screenshot as well (previously I was able to see Integration services as well but now after the repair I can't).
I'm using Visual Studio Enterprise 2017 on a test server that a few people have access to (I've also tried to restart the Visual Studio and the server but it didn't help).
Hope I can get some suggestions here, really appreciated.
I have a Visual Studio 2013 solution that includes a Windows 8.1 WinJS app along with a MVC web application. When we build the solution locally in Visual Studio, it works fine, but building it on the build server fails with the following error:
"The target "GetSolutionConfigurationContents" does not exist in the project."
Could it be a software versioning issue between the local environment and what is installed on the build server? Any ideas would be helpful tracking this down.
Thanks.
The problem was in the package.appxmanifest file.
Under the Packaging tab, I had set the "Generate app bundle" option to "Always".
Setting it to "If needed" fixed the issue and the builds are now successful.
UPDATE:
The problem reoccurred when we targeted x64 builds only, so we had to keep this project setting:
<AppxBundlePlatforms>neutral</AppxBundlePlatforms>
I have a C# WPF project I can open just fine in VS 2010 Ultimate or 2013 Ultimate.
I can edit it and run it from either.
When I double click the window.xaml, it crashes 2013.
I disabled then uninstalled my extensions. Still crashes.
I spent more than half the day uninstalling (uninstall is broken, btw) and re-installing VS 2013 Ultimate. Still crashes.
Per comment, here's a screenshot of the error:
Actually just tried to create a clean WPF project and it crashes the same way while attempting to create a new WPF project.
Always check this folder for any VS errors
%APPDATA%\Microsoft\VisualStudio\PUTYOURVSVERSIONHERE\ActivityLog.xml
If the folder doesn't exist or is empty, run Visual Studio with this command:
devenv.exe /log
There could be many reasons. This one for example was because of an outdated driver. There may be workarounds, however which one to use will depend on the error you see. Can you update your question with the error message?