Product, version and build:
64 bit version of product:
Operating system:
64 bit OS:
I've just upgraded and when I run a project I get many exceptions - load for assemblies, small subset shown below:-
ERROR:
ERROR: Exception calling "Load" with "1" argument(s): "Could not load file or assembly 'System.ServiceProcess, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f
ERROR: 7f11d50a3a' or one of its dependencies. The system cannot find the file specified."
FSRMUtility.psf: ERROR: At Line: -26 char: 35
ERROR: + [void][reflection.assembly]::Load <<<< ('System.ServiceProcess, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a')
ERROR: + CategoryInfo : NotSpecified: (:) [], MethodInvocationException
ERROR: + FullyQualifiedErrorId : DotNetMethodException
ERROR:
ERROR: Exception calling "Load" with "1" argument(s): "Could not load file or assembly 'System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a
ERROR: 3a' or one of its dependencies. The system cannot find the file specified."
FSRMUtility.psf: ERROR: At Line: -25 char: 35
ERROR: + [void][reflection.assembly]::Load <<<< ('System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a')
ERROR: + CategoryInfo : NotSpecified: (:) [], MethodInvocationException
ERROR: + FullyQualifiedErrorId : DotNetMethodException
ERROR:
I've seen the previous post "After update to PSS 2016 Assemblies not found error", downloaded the AssemblyCompatibility.cache zip, extracted and installed to PowerShell Studio 2016 folder. Restarted Powershell, however, I get the same errors. I've created a default project with a blank form and same errors.
Any help most appreciated.
Regards
Ian
Assembly errors after upgrade to 2016
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
Re: Assembly errors after upgrade to 2016
System.ServiceProcess isn't installed on all machines and the reference can be safely removed. As for System.Design I'm not sure why it is there. I recommend removing these references in the script editor:
Ribbon->Home->Edit->Assemblies
You should also remove them these assemblies if they are listed in the Default Assemblies under Options->Assemblies.
I recommend removing directly in the registry instead of the UI because there is a bug when removing default assemblies using the options. This bug is fixed in the upcoming build.
HKEY_CURRENT_USER\Software\SAPIEN Technologies, Inc.\PowerShell Studio 2016\Editor\Default Assemblies
David
Ribbon->Home->Edit->Assemblies
You should also remove them these assemblies if they are listed in the Default Assemblies under Options->Assemblies.
I recommend removing directly in the registry instead of the UI because there is a bug when removing default assemblies using the options. This bug is fixed in the upcoming build.
HKEY_CURRENT_USER\Software\SAPIEN Technologies, Inc.\PowerShell Studio 2016\Editor\Default Assemblies
David
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: Assembly errors after upgrade to 2016
I've removed assemblies from Edit, and removed the default assemblies.
Running project makes no difference.
The registry shows nothing under the registry key itself (do I have to remove the Default Assemblies key itself?)
Restarted Powershell Studio and same problem, but default assemblies returned.
Ian
Running project makes no difference.
The registry shows nothing under the registry key itself (do I have to remove the Default Assemblies key itself?)
Restarted Powershell Studio and same problem, but default assemblies returned.
Ian
Re: Assembly errors after upgrade to 2016
Please try the latest service build v5.2.116.
David
David
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.