Closed DSCmattb closed 4 years ago
try running VS as Admin
Confirmed running as administrator solved fault, cheers.
Hi @apobekiaris I'm having the same issue. Are you able to provide some info on why this occurs. It's pretty out there to require VS to be run as Admin to get things working. This isn't a requirement when working with XAF generally so don't really understand why this should necessary for expand.
ModelMapper uses reflection to load dependencies as they are not known at compiletime. The VS ME has issues to understand the actuall location of the assemblies. Threfore we use the Xpand.VSIX to copy the assemblies a special folder on each build as per
the folder contents take priority and VS ME works as usual. You could parametrize it further I guess by explicilty setting permission to this folder so admin elavation is not required, however it is not a priority task. If you think you want to do it PR are acceptable.
Thanks @apobekiaris that helps explain it. Is there any way to avoid it or just gotta run VS with elevated to admin. I presume that's why you need VSIX also.
I posted the related code above, it is not parametirized as discussed previously
Closing issue for age. Feel free to reopen it at any time.
.Thank you for your contribution.
Describe the bug Opening the Model Editor with the ImportWizard included throws the following errors:
When I go to that folder I do not see the path specified for netstandard.dll.
From my understanding it was included in .net core 2+ which I have all versions from 2-3 installed in both x64 and x86.
Desktop (please complete the following information): Win 10 1903 Visual Studio 2019 .Net 4.6.2