search

andyQn / protobuf-net

Automatically exported from code.google.com/p/protobuf-net
Other
0 stars 0 forks source link

Precompiler failed to process asm which targets .NET Framework 3.5 #456

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Please include an e-mail address if this might need a dialogue!
==============

What steps will reproduce the problem?
1. precompile asm which targets .NET Framework 3.5
2. detected as v2.0.50727
3. error
All assemblies must be resolved explicity; did not resolve: System.Core, 
Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

What is the expected output? What do you see instead?
Successfully precompiled.

What version of the product are you using? On what operating system?

Commit: e601b359c6ae56afc159754d29f5e7d0f05a01f5 [e601b35]
Date: 2015 May 26 19:10:00

Please provide any additional information below.

Assembly that target .NET Framework 3.5 has ImageRuntimeVersion attribute as 
"v2.0.50727",
So TryInferFramework(string path) returns 
"%windir%\Microsoft.NET\Framework\v2.0.50727".

However, the assembly may require not only 
"%windir%\Microsoft.NET\Framework\v2.0.50727" but also 
"%ProgramFiles%\Reference Assemblies\Microsoft\Framework\v3.5", and 
precompile.exe outputs the error.

When I add parameter "-f:v3.5 ", it reference only "%ProgramFiles%\Reference 
Assemblies\Microsoft\Framework\v3.5", but not 
"%windir%\Microsoft.NET\Framework\v2.0.50727".

How can I add both of there to probePaths?

Original issue reported on code.google.com by keii...@kei-1.jp on 3 Jun 2015 at 5:54

GoogleCodeExporter commented 8 years ago 
Any update on this?

Original comment by T...@aimproductions.be on 21 Jul 2015 at 12:52

GoogleCodeExporter commented 8 years ago 
I'm using attached patch.

Original comment by keii...@kei-1.jp on 24 Jul 2015 at 8:43

Attachments: