Unable to add assemblies with same name but different version
Posted: Mon Dec 25, 2017 7:19 pm
To help you better we need some information from you.
*** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. ***
Product, version and build: SAPIEN PowerShell Studio 2017 Version 5.4.145
32 or 64 bit version of product: 64 bit
Operating system: windows 10 version 1703
32 or 64 bit OS: 64
*** Please add details and screenshots as needed below. ***
Ok. So this might be a unique issue, but I am working on a project which requires the use of many external assemblies (that I was hoping to integrate into the project with the assemblies feature). There is one assembly in particular (Newtonsoft.Json) which the project requires that two different versions of the same assembly be imported from into the running session (need version 10.0.3 which I obtain via nuget, and 9.0.1 which is included in the dot net core sdk). However, it would appear that powershell studio will not allow to import both versions of the assembly due to the fact that they have the same name, which essentially means that I cannot use powershell studio as I was hoping to and embedding the assemblies in the script. I understand that the product was probably designed this way in order to prevent users from adding duplicate assemblies to the same project, but I would very, very, very, very, very, very much recommend that the version of the assemblies be considered when the product determines duplicate assemblies and either adds or does not add them to the project.
DO NOT POST SUBSCRIPTIONS, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM
*** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. ***
Product, version and build: SAPIEN PowerShell Studio 2017 Version 5.4.145
32 or 64 bit version of product: 64 bit
Operating system: windows 10 version 1703
32 or 64 bit OS: 64
*** Please add details and screenshots as needed below. ***
Ok. So this might be a unique issue, but I am working on a project which requires the use of many external assemblies (that I was hoping to integrate into the project with the assemblies feature). There is one assembly in particular (Newtonsoft.Json) which the project requires that two different versions of the same assembly be imported from into the running session (need version 10.0.3 which I obtain via nuget, and 9.0.1 which is included in the dot net core sdk). However, it would appear that powershell studio will not allow to import both versions of the assembly due to the fact that they have the same name, which essentially means that I cannot use powershell studio as I was hoping to and embedding the assemblies in the script. I understand that the product was probably designed this way in order to prevent users from adding duplicate assemblies to the same project, but I would very, very, very, very, very, very much recommend that the version of the assemblies be considered when the product determines duplicate assemblies and either adds or does not add them to the project.
DO NOT POST SUBSCRIPTIONS, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM