Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong project reference resolution on Release mode #150

Closed
KevinRansom opened this issue Jan 27, 2015 · 2 comments
Closed

Wrong project reference resolution on Release mode #150

KevinRansom opened this issue Jan 27, 2015 · 2 comments

Comments

@KevinRansom
Copy link
Member

Opened on CodePlex by dungpa

Visual F# Tools' project system resolves project references to Debug mode although the current project is on Release mode. Here is an excerpt of FSharpProjectOptions that shows the issue:

GetProjectCheckerOptions: ProjectFileName: C:\VFPT\tests\FSharpVSPowerTools.Tests\FSharpVSPowerTools.Tests.fsproj, ProjectFileNames: [|"C:\AppData\Local\Temp.NETFramework,Version=v4.5.AssemblyAttributes.fs";
 "C:\VFPT\tests\FSharpVSPowerTools.Tests\ProjectParser.fs";
 "C:\VFPT\tests\FSharpVSPowerTools.Tests\ExternalProjectProvider.fs";
 "C:\VFPT\tests\FSharpVSPowerTools.Tests\TestHelpers.fs";
 "C:\VFPT\tests\FSharpVSPowerTools.Tests\MockDTE.fs";
 "C:\VFPT\tests\FSharpVSPowerTools.Tests\Mocks.fs";
 "C:\VFPT\tests\FSharpVSPowerTools.Tests\VsTestBase.fs";
 "C:\VFPT\tests\FSharpVSPowerTools.Tests\SyntaxConstructClassifierTests.fs";
 "C:\VFPT\tests\FSharpVSPowerTools.Tests\ResolveUnopenedNamespaceSmartTaggerTests.fs";
 "C:\VFPT\tests\FSharpVSPowerTools.Tests\HighlightUsageTaggerTests.fs";
 "C:\VFPT\tests\FSharpVSPowerTools.Tests\FormattingTests.fs";
 "C:\VFPT\tests\FSharpVSPowerTools.Tests\DepthTaggerTests.fs"|], FSharpProjectOptions: [|"-o:obj\Release\FSharpVSPowerTools.Tests.dll"; "--debug:pdbonly";
 "--noframework"; "--define:TRACE";
 "--doc:bin\Release\FSharpVSPowerTools.Tests.XML"; "--optimize+";
 "--platform:anycpu";
 "-r:C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PublicAssemblies\EnvDTE.dll";
 "-r:C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PublicAssemblies\EnvDTE80.dll";
 "-r:C:\VFPT\packages\Foq\lib\net45\Foq.dll";
 "-r:C:\VFPT\packages\FSharp.Compiler.Service\lib\net45\FSharp.Compiler.Service.dll";
 "-r:C:\Program Files (x86)\Reference Assemblies\Microsoft\FSharp.NETFramework\v4.0\4.3.0.0\FSharp.Core.dll";
 "-r:C:\VFPT\packages\FSharp.ViewModule.Core\lib\net45\FSharp.ViewModule.Core.Wpf.dll";
 "-r:C:\VFPT\src\FSharpVSPowerTools.Core\bin\Debug\FSharpVSPowerTools.Core.dll";
 "-r:C:\VFPT\bin\FSharpVSPowerTools.dll";
 "-r:C:\VFPT\src\FSharpVSPowerTools.Logic\bin\Debug\FSharpVSPowerTools.Logic.dll";

Notice that *.Core.dll and *.Logic.dll refer to their bin\Debug folders.

It sounds strange but this affects Visual F# Power Tools as a client because we rely on resolution information from Visual F# Tools' project system.

Downstream bug report fsprojects-archive/zzarchive-VisualFSharpPowerTools#790

comments
latkin wrote Nov 25, 2014 at 5:37 PM [x]
Can you provide a repro solution?

@dsyme
Copy link
Contributor

dsyme commented Jan 27, 2015

This now definitely needs a repro solution, as per the updated CONTRIBUTING.md guidelines. We should close for now I guess

@dungpa - can you provide a repro solution?

@dungpa
Copy link
Contributor

dungpa commented Jan 27, 2015

The issue appears to be intermittent. Feel free to close.

I'll request to reopen the issue if I find a definite repro.

@latkin latkin closed this as completed Jan 27, 2015
latkin added a commit that referenced this issue Aug 14, 2015
…dClosures.FSharpFunc<_>.Adapt (changeset 1364854)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants