Skip to main content
Has anyone experienced K2.net 2003 SP4 Studio crashing when using a custom reference DLL in code design?
Does this happen to be a .NET 2.0 assembly that you are referencing? Is the K2.net Studio on your machine configured to run .NET 2.0?

Refer to KB 154 (http://kb.k2workflow.com/Articles/KB000154.aspx) to see how what version of the .NET Framework K2 Studio is configured to use.
I ran through that article, and both the server and the studio were setup to use the 2.0.50727. I didn't think that the server would be the cause because we haven't compiled yet from K2 Studio.
My thought was this may have been a .NET 2.0 assembly trying to be referenced by .NET 1.1 app (K2 Studio).
I do wish that it would have been that easy as well.
Is it a .NET 1.1 DLL that you're attempting to reference in a Studio/Server environment that is tied to .NET 2.0?
icon-quote.gifK2Moto:
Is it a .NET 1.1 DLL that you're attempting to reference in a Studio/Server environment that is tied to .NET 2.0?


you should still be able to reference a .NET 1.1 DLL from .NET 2.0

Hi dsSubLette,


I am having the similar problem you described.


My case is - after an external assembly is referenced, when we attempted to type the following statement for creating an instance of a class, i.e.


myClass oo = new myClass();


Studio crashed.


It is repeatable each time if you add a new constructor paramter to the function. For example, after we modified the constructor for using one parameter, studio will crash when we type:


myClass oo = new myClass(param1); // and so on for myClass(param1, param2 ....)


I communicated with couple of Studio experts and I heard that the following could resolve the problem:


(1) Uninstall FW2.0 and reinstall.


(2) Remove the Code Editor and use the old one


The workaround for now is to write the code in Visual Studio and then cut and paste them back to K2 Studio.


Does anyone has the same experience or can suggest a better workaround?


Thanks,


Marco


Hi,


We have been working on this issue before and unfortunately the only solutions are to :



  • Uninstall FW2.0 and Reinstall. If this doesn't do the thing,
  • Revert back to the old editor.

If you are not prepared to reinstall your FW you can just revert back to the old editor. You  can test that it is a framework issue by simply changing the Studio config file to use FW1.1.(Note that you have to use the full framewolrk version.)


Cheers


Gert


Reply