search

MethodsAndPractices / vsteam

PowerShell module for accessing Azure DevOps Services and Azure DevOps Server (formerly VSTS or TFS)
https://methodsandpractices.github.io/vsteam-docs/
MIT License
444 stars 155 forks source link

Local Development and Testing causes Problems when published VSTeam module is installed on the same machine #404

Closed SebastianSchuetze closed 2 years ago

SebastianSchuetze commented 3 years ago

I noticed during development and running unit tests the you run into the following error:

assembly with same name is already loaded

In this case we talk about the generated dll. And it go clear to me why. For one, the installed and published module is imported when opening session. When I then build the module locally and during unit tests the built module is imported, then the above error comes up.

I think this is how we can solve it: The built dll should have a temporary unique naming / id so that it is interpreted as a different one. I am not sure if changing the name of the DLL is enough. But I think some other things would need to change as well.

But if we could make this possible, then development would be easier I think.

SebastianSchuetze commented 2 years ago

closing this in favor for other things. Not too important.