I have an WCF service on Azure with diagnostics/logging enabled. The project is already existing for some time and transitted through Visual Studio 2012, 2013 and now 2015. I discovered there is two diagnostics.wadcfg(X) files.
Can I remove diagnostics.wadcfg?
Where I can find some information on .wadcfg and .wadcfgx? Meaning what Microsoft Tooling was upgraded at some point in time that we now need .wadcfgx?
Thanks. BR, Rene
wadcfg can be safely removed and so is the reference to Azure Diagnostics -- assuming you've upgraded to Azure SDK 2.5+
Related
This error just started occurring on a few developers' systems across several packages, but I can't track down a specific cause or update. We have SSIS processes created across various targets (SQL 2012 and up), but when I open them in Visual Studio 2019 this error occurs:
Error loading XXXXXXX.dtsx: There was an exception while loading Script Task from XML: System.Exception: The Script Task "ST_36ae893a14204fac97ce8ce3b4ce8ebb" uses version 16.0 script that is not supported in this release of Integration Services. To run the package, use the Script Task to create a new VSTA script. In most cases, scripts are converted automatically to use a supported version, when you open a SQL Server Integration Services package in %SQL_PRODUCT_SHORT_NAME% Integration Services.
at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTask.LoadFromXML(XmlElement elemProj, IDTSInfoEvents events)
I can open the script task, but it's as if it's new, none of the existing code is there. Some of the older packages I can open in like Visual Studio 2017 and they work, but in Visual Studio 2019 not so much. Even some packages built in Visual Studio 2019 are doing this. Here's my dev environment:
Microsoft Visual Studio Enterprise 2019
Version 16.11.17
VisualStudio.16.Release/16.11.17+32630.194
Microsoft .NET Framework
Version 4.8.04084
SQL Server Data Tools 16.0.62205.05200
Microsoft SQL Server Data Tools
SQL Server Integration Services 16.0.948.0
Microsoft SQL Server Integration Services Designer
I've tried changing the Target server to different versions, but it seems once the issue occurs it resets the script task removing all code. I'm really confused.
Any thoughts? Thanks.
Not sure if this is a good answer, but it does seem to fix the issue. I'm using SQL Server Integration Services 16.0.948.0 (v4.3), but if I go back down to 15.0.2000.180 (v3.16) the issue seems to go away. So, it's something with version 4.0 and up. Not ideal to go backwards as we're losing some of the updates - but it gets me going again. If anyone has other suggestions, please let me know.
I installed VS 2022 Community and am trying to work on a project that was developed on VS 2008 Pro. VS is giving me this report:
How do I force VS to make whatever upgrades it needs in order to run this program? I can provide more info if needed.
MS in their wisdom, dropped support for the Setup & Deployment project, can't remember when exactly, then after a bit of an uproar re-instated it through the Visual Studio marketplace https://marketplace.visualstudio.com/items?itemName=VisualStudioClient.MicrosoftVisualStudio2017InstallerProjects
Since your project has a file .vddproj, it might be a Smart Device CAB project.
It is not supported by later versions of visual studio.
It is recommended that you open it with VS2008.
We have on-prem Azure DevOps 2020 installed. We built a .net core 6 app in Visual Studio 2022.
However, when creating the build pipeline, VS 2022 is not showing up in the dropdown.
Has anyone faced this problem? Is MSFT supposed to release a patch that will start displaying VS 2022 in the dropdown?
Many people are running into this. No word from MS yet on when or if an update will be available. But these articles may help you find a workaround:
How do I update my Azure DevOps on-premise Pipeline tasks to include MSBuild v17 and Visual Studio 2022?
https://jessehouwing.net/adding-visual-studio-2022-to-azure-devops-server-2020/
https://github.com/microsoft/azure-pipelines-agent/issues/3662
FWIW, I'm working around it by using an explicit MSBuild path as mentioned in this answer. I added a PreferredMSBuildExePath variable to my pipeline and set it equal to %ProgramFiles%\Microsoft Visual Studio\2022\Professional\MSBuild\Current\Bin\amd64\MSBuild.exe. Then I made all my MSBuild steps use $(PreferredMSBuildExePath) as their MSBuild path under Specify Location. I also converted all my Visual Studio steps to MSBuild steps so I could use this explicit path variable.
VS 2012 published web service and click once deployment of a Windows forms application based on VB.NET and .Net 4.0 don't serve up the newer version of the software. They keep on serving the previous version. However it works fine with VS 2010. This is on IIS 7/7.5.
Anyone have any idea about it?
Thanks.
Never mind. I had to clean and rebuild. VS 2012 added an extra step over 2010.
I've used MS Visual Basic 2010 Express to build a very simple VB.Net Windows app. I need to check the code into our Team Foundation Server Source Control. Is there a TFS plug-in for VB Express? If not, do I need to check the code in manually?
You will have to do it manually as stated here .
Given my experience with TFS I would check the code in manually. Package it all up nicely and get one changeset for the lot.
TFS isn't supported in any of the express editions of Visual Studio. I'm not sure if TFS is integrated into Windows Explorer for manually updates and commits. Other with experience would need to comment.