I'm hoping someone can help me with this. How do I go about using VS Code to develop on Biztalk 2016?
Let me explain further...
Currently, I have to install Biztalk Server on my PC. Then in Visual Studio a Biztalk project template will be available. I create a new project from this template and voila!
Is it possible to do something like this with VS Code?
Any guidance would be much appreciated.
VS Code is currently unsupported for BizTalk 2016 project files.
Related
I am trying to make the Word Web Addin project template (that came with Visual Studio) to work. When starting the project, without modifying anything, I am stuck with the following message :
I have no clue how to troubleshoot this. I've searched on google but most stuff with Visual Studio is about VSTO solutions which is not the case here. Tried both VS2017 and VS2019 with no luck.
Any ideas how to investigate this ?
btw: I'm on Windows version 10.0.14393 with office 2019 / Word version 1911.
Can't tell why but after updating my Visual Studio without success, I made a "repair" installation of my VS2019 and it finally worked.
I'm looking to create a very simple UI plugin for Windows Media Player, similar to this: https://obsproject.com/forum/resources/windows-media-player-title-artist-text-output-ticker.402/, but with the ability to choose the path and name of the text file.
I haven't been able to find any answers to WMP Plugin development questions on here since 2013, and the last actual answer give was for Visual Studio 2008. I'm now using Visual Studio 2019, so almost all of the tutorials, guides, and FAQs are massively out of date.
I've been following the setup guide here: https://learn.microsoft.com/en-us/previous-versions//aa969437(v=vs.85)?redirectedfrom=MSDN
After a few hours, I've finally been able to install the Windows 7.1 SDK by deleting all my C++ 2010 redistributables, and temporarily rolling back my .NET Framework 4 version to RTM. I now have wmpwiz.ico, wmpwiz.vsdir, and wmpwiz.vsz.
The interal version of VS2019 is 16.0, so I've edited my wmpwiz.vsz file to read:
VSWIZARD 7.0
Wizard=VsWizard.16.0
Param="WIZARD_NAME = Windows Media Player Plug-in Wizard"
Param="ABSOLUTE_PATH = C:\Program Files\Microsoft SDKs\Windows\v7.1\Samples\multimedia\WMP\Wizards\wmpwiz"
Param="FALLBACK_LCID = 1033"
and I've placed the three files into %UserProfile%\Documents\Visual Studio 2019\Templates\ProjectTemplates\Visual C++ Project\, but nothing shows up in the Start New Project window.
Obviously, I'm using technology that hasn't been touched for over a decade, so I don't know if this approach will even work anymore. Are there any modern guides on how to do this, or would it be quicker and easier to try to dig out my old VS2005 install disks, and hope they're not too scratched?
If this SDK Sample has been depreciated with age, are there any other wizards available that can be used for WMP plugin development? Preferably using C#, as I'm a .NET programmer, but I'm happy to trawl through C++ if I absolutely have to.
Thanks for any help you can give.
I am trying to Deploy Acumatica Framework Tools using the Framework Configuration Wizard and I getting the following error:
Exception occurred while installing resources.
Inner Exception:
Can't find the Visual Studio template items location.
I have Visual Studio 2017 Enterprise running on Windows 10 Pro. Both are up to date.
Any ideas on how to correct this. I’m going to the Acumatica Summit next week and need to do the T100 and T200 course.
Thanks
Tom
The wizard is likely looking for the VS2015 registry folder. Until installers are fixed to check in the VS2017 location I recommend you create the VS2015 registry folders with these 4 dummy string keys pointing to VS2017 folder.
The key values in the picture below point to the default VS2017 folders. I tested this workaround a couple months ago on a colleague computer and we experience no ill effects:
I faced the same problem, but I could not change my registry due to company policy. My regedit.exe was unavailable:
So, to fix this issue I installed Visual Studio 2015 Community Edition .
That fixed the issue.
Do not forget to restart your computer after installation, otherwise - you will get the same error. If you solve this problem with installation of VS2015, you will be able to use Visual Studio Template
in VS2015 only. It will not be available in other versions of Visual Studio.
The msi file created by the VS2010 setup/install project does not install on Windows 2000. One will see a message like: "the procedure entry point GetNativeSystemInfo was not found" I can use a VS2008 setup project to solve this. What VS2010 solution is there to this problem?
Advanced Installer can create a setup working on Win2K, it has a free version too.
Went with InstallShield LE which is integrated into VS and is free.
What would be the most frictionless workflow for working with NuGet and Visual Studio 2005? Is this at all possible? I understand that the plugin is only available for Visual Studio 2010, but there is still the package manager console wich seems to be nothing more than powershell. Can I run the console without Visual Studio and can the console download and integrate packages into visual studio 2005 projects? If so, how is this done?
Scott Hanselman blogged about adding NuGet "support" to Visual Studio 2008. You can probably adapt this slightly to work in Visual Studio 2005 too, though of course you won't get the same experience as in Visual Studio 2010.
Well, not really. A better title would be "How to Cobble Together
NuGet Support for Visual Studio 2008 with External Tools and a
Prayer." The point is, there are lots of folks using Visual Studio
2008 who would like NuGet support. I'm exploring this area and there's
a half-dozen ways to make it happen, some difficult and some less so.
The idea would be to enable some things with minimal effort. It'll be
interesting to see if there are folks in the community who think this
is important enough to actually make it happen. Of course, the easiest
thing is to just use 2010 as it sill supports .NET 2.0, 3.0, 3.5, and
4, but not everyone can upgrade.
Someone could:
Backport the existing NuGet Package References dialog to 2008 using
that version's native extensions (not VSiX)
Create MEF (Managed
Extensibility Framework) plugins for the nuget.exe command-line to
update the references in a vbproj or csproj
Use PowerShell scripts and
batch files to get the most basic stuff working (get a package and
update references.)
Maybe write a shim to get DTE automation
working...
But that's coulds and maybes. Let's talk about the MacGyver
solution. more »