2

While working on two Visual Studio solutions, one of which depends on the other, if I build the dependency the other 'master' project seems to lose track of the dependency, but only as far as intellisense and syntax highlighting.

So the master project can compile just fine but the red squigglies will tell me that any types defined in the dependency don't exist. If I close and reopen the solution (or unload and reload the project) things return to normal, until such time as I need to make a change in the dependency again.

Has anyone encountered similar issues and if so is there a solution other than having to close and reopen Visual Studio or unload and reload the project?

Derf Skren
  • 479
  • 2
  • 22
  • 1
    It's unusual to have dependencies between **solutions**. Typically you have dependencies between **projects** within one solution. – user1620220 Jul 07 '16 at 01:04
  • LOL OK then I'll just tell my organisation that they're doing things wrong and that all our software from actual products through to automated tests should live in one solution that 30-40 people work on simultaneously. – Derf Skren Jul 07 '16 at 01:11
  • Unusual doesn't mean wrong. Perhaps ask one of the 30-40 other people if they've had the same issue... – user1620220 Jul 07 '16 at 01:46
  • And see [Microsoft's recommendations](https://msdn.microsoft.com/en-us/library/ee817675.aspx) on the matter. – user1620220 Jul 07 '16 at 01:58
  • It's not unusual though, is it? And I've already asked other people in my organisation which is why I'm forced to endure conversations like this in the hopes of getting an answer. As for the article about setting up dependencies using Team Development with Source Safe from 2002, so far it's not helping me identify what's changed between Visual Studio 2010 and 2015 that's making this standard feature stop working. – Derf Skren Jul 07 '16 at 02:15
  • Try a clean and rebuild. – NikolaiDante Jul 17 '16 at 17:36
  • Just rebuild solution? – Ppp Jul 18 '16 at 02:25
  • The solution builds fine. No combination of cleaning/rebuilding either the dependency or the solution in question does anything to the syntax highlighting or intellisense suggestions. – Derf Skren Jul 18 '16 at 04:41
  • did you reference the dll or the project from the other solution (include the project to your solution)? – Ppp Jul 18 '16 at 09:42
  • @Ppp yes, as I said the solution builds correctly. – Derf Skren Jul 24 '16 at 23:29
  • 1
    @user1620220 why is it unusual to have dpendencies between solutions? Isn't the idea of a DLL to contain solutions to a general problem that can be consumed by multiple different applications? – Michael Ribbons Feb 19 '20 at 00:14
  • @MichaelRibbons Yes, but if you are developing two DLLs and there is a dependency between them (like in OP's situation) it is better to load them into a single solution for the reasons outlined in the article I linked. And as OP found out VS just handles it better. – user1620220 Feb 20 '20 at 19:54
  • 1
    @user1620220 That's a rather long article. Can you paste the paragraph lead in for the part you are referring to? – Michael Ribbons Feb 20 '20 at 21:11
  • 1
    @user1620220 Where did OP say putting everything in one solution worked for him? – Michael Ribbons Feb 20 '20 at 21:13

1 Answers1

1

Derf Skren!

I do not think there is a solution I cannot seem to find it I will report this to Microsoft for you and I would try unloading and reloading it as that may work.

Hopefully, that works,
Liam

Liam
  • 1,179
  • 1
  • 7
  • 22
  • Thanks Liam, as I outlined in the question, unloading and reloading does work but I still can't work out why the problem occurs and why this is broken in 2015 but not 2010. – Derf Skren Jul 18 '16 at 04:42