M
Mike Fechner
Guest
Hi, I am currently working on a project where we are developing parts of an application as custom .NET assemblies in Visual Studio. It get's hardly annoying that we have to stop PDSOE completely in order to be able to replace a .NET Assembly with a new version - as we may have to do that every couple of minutes. I'd rather just have to "restart project AVM" on those projects that rely on the updated assembly. Is there a chance to use the .NET Assembly Shadow Copying with PDSOE and the Progress runtime processes? https://msdn.microsoft.com/en-us/library/ms404279(v=vs.100).aspx My understanding is, that both the java portion of the PDSOE tools as well as the prowin.exe|prowin32.exe hold a file lock on any referenced Assembly and thus preventing us to replace it with a newer version. So we'd have to update enable the Shadow Copying for the prowin processes and probably javaw.exe. I tried to run this code here: USING System.* FROM ASSEMBLY. MESSAGE "shadow?" AppDomain:CurrentDomain:ShadowCopyFiles VIEW-AS ALERT-BOX. And it shows "no". Is there a way to change this? I tried various settings in prowin32.exe.config - but with no luck so far.
Continue reading...
Continue reading...