Unable to build sample project in Visual Studio about codegeneration.roslyn

[orellabac]

@Pzixel mmm I was able to reproduce your issue by using a similar path to what you are using.
I do not know yet if the path has any influence. But I will be checking it.

[Pzixel]

Bug is fixed in VS2017 update 2.

[masaeedu]

@Pzixel Seems like a flaky issue. I don't know if you have a cloud storage account (onedrive/dropbox etc.), but if you could take a snapshot of a VM in which you've reproduced the issue and share the files we can experiment with it. I've personally been using the nuget packages in VS 2017 preview, and haven't had any issues. Even managed to implement XML type providers for C# 😄

[masaeedu]

@Pzixel Are you applying the attribute in the same project where you have your code generator defined?

[Pzixel]

@masaeedu I haven't this code changed at all. I just did git clone & start vs & build solution

[masaeedu]

@Pzixel Is this a consistent issue across machines? Maybe try nuking your repo and trying again. I just tried the following and get a successful build:

git clone [email protected]:AArnott/CodeGeneration.Roslyn.git
cd .\CodeGeneration.Roslyn\src
dotnet restore
msbuild .\CodeGeneration.Roslyn.sln

[Pzixel]

@masaeedu yes, it works (a little win here).

However, if you build solution through VS you get these errors:

[masaeedu]

@Pzixel The actual problem seems to be: The 'GenerateCodeFromAttributes' task failed unexpectedly. System.MethodMissingException: Method not found: '...ImmutableArray`1<SyntaxTree>'. Did you restore your nuget packages?

[Pzixel]

@masaeedu I ran VS build after building in console thus all packages have to be restored.

[Pzixel]

No idea what's wrong here?

[orellabac]

@Pzixel Isee from the screenshot that the console build was run as administrator. Are you running the VS as administrator too?

[Pzixel]

@orellabac of course. I even set compatibility mode this programm require additional permisions when I install VS to be sure that it's always in administrator mode.

[Pzixel]

@orellabac Few days later I tried to build it again, and encountered this issue again. So it's not being fixed by update2. I can provide any additional information but I don't really know what's causing the issue.

[Pzixel]

@masaeedu good idea. However, I'm not really sure if it's easy to share 30gb-minimum-image of VM where this issue is reproducable. However, I think it's a good idea to test on fresh VM, because it may be environment problem.

To be honest, if I add CodeGeneration.Roslyn as NuGet reference, it works fine. So I can continue my work anyway. It's just an interesting case, because I was thinking that it would be easier to download a whole sample and study it while now it seems very complicated :)

[Pzixel]

Ok, I just installed the freshest W10 and VS and was able to repro this issue. I'm studying how can I share it (it's 50 GB), becuase I have only 30GB in my OneDrive. I'd appreciate If someone know any free service where I can upload it.

[Pzixel]

Here is link to my OneDrive folder. It's HyperV VM, 7gb archived, 20gb unzipped. Issue is totally reproducable there.

[Pzixel]

Hey, what I found! If you open visual studio and try to compile form msbuild you get the same error! :)

[Pzixel]

This could be solved with killing all msbuild processes and starting build (not rebuild) again.

[Pzixel]

So, There is a workaround, but issue is still here.

[amis92]

File locks are no longer an issue since v0.4.74 by #83, I think?

[Pzixel]

Hmm, interesting. Gonna check it later, thank you.

[AArnott]

Ya, I thought #83 would have avoided this. Otherwise, what I tended to do was unload the project that couldn't build since it rarely needed to build during regular development in the sln anyway.

[amis92]

I'll close this as it's possibly resolved, and I can't repro it with current master.