Skip to content
This repository has been archived by the owner on Oct 31, 2021. It is now read-only.

"Not all referenced projects are in the compiler options" assert popups in Release configuration #790

Closed
vasily-kirichenko opened this issue Oct 22, 2014 · 7 comments
Closed

"Not all referenced projects are in the compiler options" assert popups in Release configuration #790

vasily-kirichenko opened this issue Oct 22, 2014 · 7 comments
Labels
bug upstream

Comments

@vasily-kirichenko
Copy link
Contributor

image

@dungpa I believe it started to popup after you introduced getCurrentProject. On my solution at work this dialog appears almost every time I open a file in a project no files from which are already opened.
@vasily-kirichenko vasily-kirichenko changed the title "Not all referenced projects are in the compiler options" assert started popups all the time "Not all referenced projects are in the compiler options" assert started to popup all the time Oct 22, 2014
@dungpa
Copy link
Contributor

dungpa commented Oct 22, 2014

Are your projects on 'Release' mode? If yes, it's a known issue with FCS' assembly resolution that causes the assertion to fail in this case.

@vasily-kirichenko
Copy link
Contributor Author

Aha! Yes, it was in Release config. I switched to Debug and everything is ok now. Wow, this is a huge bug in FCS :(

@vasily-kirichenko vasily-kirichenko changed the title "Not all referenced projects are in the compiler options" assert started to popup all the time "Not all referenced projects are in the compiler options" assert popups in Release configuration Oct 22, 2014
@dungpa
Copy link
Contributor

dungpa commented Oct 22, 2014

I'll work out the details and report upstream.

dungpa added a commit to dungpa/PowerTools that referenced this issue Oct 22, 2014
@dungpa
Protect against exceptions in automatic features
0043355 
Use 'protectOrDefault' and 'protect' wherever possible.
Possible fix for fsprojects-archive#790.
@dungpa dungpa mentioned this issue Oct 22, 2014
Merged
dungpa added a commit to dungpa/PowerTools that referenced this issue Oct 22, 2014
@dungpa
Protect against exceptions in tag-based features
b1e812f 
Use 'protectOrDefault' or `protect` wherever possible.
Possible fix for fsprojects-archive#790.
@dungpa dungpa mentioned this issue Oct 27, 2014
Closed
@dungpa
Copy link
Contributor

dungpa commented Oct 28, 2014

Turned out I was wrong. The issue comes from Visual F# Tools (see https://visualfsharp.codeplex.com/workitem/164).

@dsyme
Copy link
Contributor

dsyme commented Oct 29, 2014

That resolution is not necessarily wrong if the "solution configuration" specifies a mix of debug and release configurations. Could you check the solution configuration just in case? I guess it would be even better if the repro on visualfsharp.codeplex.com showed how to repro this by creating a new project etc.

@dungpa
Copy link
Contributor

dungpa commented Oct 31, 2014

@dsyme It happens on multiple solutions and none of them is on mixed mode.

@KevinRansom KevinRansom mentioned this issue Jan 27, 2015
Closed
@dungpa
Copy link
Contributor

dungpa commented Mar 2, 2015

Couldn't repro cleanly. Closing since it doesn't affect any functionality.

@dungpa dungpa closed this as completed Mar 2, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug upstream
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vasily-kirichenko @dungpa @dsyme