Skip to main content
Nintex Community Menu Bar

​@EttienneS Hi, your name came up n K2 for VS 2015 package.  😁

If VS 2019 can load the K2 designer extension, the deployment functionality could work?

VS 2015 / 2017 / 2019 are highly compatible for extensions. 

Seems it just needs to change a few references to point to VS 2019 path/registry.

https://devblogs.microsoft.com/visualstudio/how-to-upgrade-extensions-to-support-visual-studio-2019/

change K2 for Visual Studio 2015.xml:

  • Reference 2019 name <AllowedDependency Type="Application" Name="Microsoft Visual Studio Professional 2019" MatchType="EqualTo" />
  • Path set to Microsoft Visual Studio 16.0

SourceCode.VisualStudio(2015).reg:

  • Reference 16.0 registry.

SourceCode.Workflow.VisualStudio (2015).reg:

  • Reference 16.0 registry.

If anyone tried this and didn’t work, chime in.   Thanks.

Hi ​@PYao 

Yes it should be as simple as that I do not see anything specifically compiled for VS2015 so if you were to tweak the registry keys and install paths to point to the right place then the install would mostly work.

The ResetToolboxes bit is probably going to be the most annoying as you would have to reverse engineer that to set the correct key.

Not something I have ever tried or anybody I know of has tried and obviously not a supported install but it should be possible.

Hope that helps

​@EttienneS   I am trying this now with VS2015 EOL in October.

Changed extension.vsixmanifest to include below allowed it to install for VS2019.

<InstallationTarget Id="Microsoft.VisualStudio.Professional"  Version="[16.0,17.0)" />

I didn’t touch the ResetToolboxes, issues encountered seem to be before that.

  • On start of VS2019 gets an error message “The ‘WorkflowPackage’ package did not load correctly.  The problem may have been caused by a configuration change or by the installation of another extension.   (more info in activityLog.xml)

    <source>VisualStudio</source>
    <description>LegacySitePackage failed for package [WorkflowPackage]  Source: 'mscorlib' Description: Version string portion was too short or too long.   SourceCode.VisualStudio.K2ProjectFactory..ctor(WorkflowPackage package)  at SourceCode.VisualStudio.WorkflowPackage.Initialize() at Microsoft.VisualStudio.Shell.Package.Microsoft.VisualStudio.Shell.Interop.IVsPackage.SetSite(IServiceProvider sp)
    <guid>{AB85DF7A-EE9A-42CB-877E-E96781A6E60E}</guid>
    <hr>80070057 - E_INVALIDARG</hr>

SetSite failed for package [WorkflowPackage]

 

SourceCode.VisualStudio.pkgdef 

"ProductVersion"="1.0"

Changed to 

"ProductVersion"="1.0.0.0"

 

If I disable SourceCode.VisualStudio extension then I don’t get the above error when I start VS2019.  VS2019 has Wndows Workflow Foundation component installed.

After the message it does start VS2019 and I see extension SourceCode.VisualStudio installed, indicating it’s using deprecated API (OK, it’s a warning).

I have also enabled Tools/Options/Extensions - Allow synchronous autoload of extensions (used for K2 extension but not recommended for VS2019).

When I load the project that contains K2 4.7 ,kprx, VS project says (incompatible).

UpgradeLog.htm   The application which this project type is based on was not found. Please try this link for further information: https://go.microsoft.com/fwlink/?LinkId=660952&projecttype=D50D8A3F-5CE1-4E89-9491-F84FAB0E386A

The above test did not run below, another dev is assisting with converting those to VS2019.

SourceCode.SmartObjects.VisualStudio(2015).reg

SourceCode.VisualStudio(2015).reg

SourceCode.Workflow.VisualStudio (2015).reg

Sidebar Buttons
Nintex Community Home Contact Nintex Support Email Nintex Community Check Nintex Status
Terms & ConditionsCookie SettingsAccessibility statement