[MonoDevelop] Problem with multi-project solution

[Stifu]

I tried and added an assembly to the unit test project: no difference.
In MonoDevelop, simply adding an existing project and attaching the unit
test one works. It modifies the sln like this:



Microsoft Visual Studio Solution File, Format Version 10.00

# Visual Studio 2008

Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "EpicEdit",
"EpicEdit\EpicEdit.csproj", "{67D2F08E-7925-4E20-A9E9-07D4CAA24B20}"

EndProject

Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "EpicEditTests",
"EpicEditTests\EpicEditTests.csproj",
"{5C404E58-B6EA-466A-B1D5-D689F97CEC50}"

EndProject

Global

	GlobalSection(SolutionConfigurationPlatforms) = preSolution

		Debug|Any CPU = Debug|Any CPU

		Release|Any CPU = Release|Any CPU

	EndGlobalSection

	GlobalSection(ProjectConfigurationPlatforms) = postSolution

		{5C404E58-B6EA-466A-B1D5-D689F97CEC50}.Debug|Any CPU.ActiveCfg = Debug|Any
CPU

		{5C404E58-B6EA-466A-B1D5-D689F97CEC50}.Debug|Any CPU.Build.0 = Debug|Any
CPU

		{5C404E58-B6EA-466A-B1D5-D689F97CEC50}.Release|Any CPU.ActiveCfg =
Release|Any CPU

		{5C404E58-B6EA-466A-B1D5-D689F97CEC50}.Release|Any CPU.Build.0 =
Release|Any CPU

		{67D2F08E-7925-4E20-A9E9-07D4CAA24B20}.Debug|Any CPU.ActiveCfg = Debug|Any
CPU

		{67D2F08E-7925-4E20-A9E9-07D4CAA24B20}.Debug|Any CPU.Build.0 = Debug|Any
CPU

		{67D2F08E-7925-4E20-A9E9-07D4CAA24B20}.Release|Any CPU.ActiveCfg =
Release|Any CPU

		{67D2F08E-7925-4E20-A9E9-07D4CAA24B20}.Release|Any CPU.Build.0 =
Release|Any CPU

		D1C35FCD-7506-4247-9396-4FEAFEC21526.Debug|Any CPU.Build.0 = Debug|Any CPU

		D1C35FCD-7506-4247-9396-4FEAFEC21526.Debug|Any CPU.ActiveCfg = Debug|Any
CPU

		D1C35FCD-7506-4247-9396-4FEAFEC21526.Release|Any CPU.Build.0 = Release|Any
CPU

		D1C35FCD-7506-4247-9396-4FEAFEC21526.Release|Any CPU.ActiveCfg =
Release|Any CPU

	EndGlobalSection

	GlobalSection(MonoDevelopProperties) = preSolution

		version = 0.1

		StartupItem = EpicEdit\EpicEdit.csproj

	EndGlobalSection

	GlobalSection(SolutionProperties) = preSolution

		HideSolutionNode = FALSE

	EndGlobalSection

EndGlobal



And it's apparently this line that makes a difference (changed project id or
something):

Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "EpicEditTests",
"EpicEditTests\EpicEditTests.csproj",
"{5C404E58-B6EA-466A-B1D5-D689F97CEC50}"


Stifu wrote:
> 
> Hi,
> 
> I have a solution with 2 projects inside, but MonoDevelop only shows the
> first one. It works fine with Visual Studio and SharpDevelop.
> Here's the sln file:
> 
> 
> 
> Microsoft Visual Studio Solution File, Format Version 10.00
> 
> # Visual Studio 2008
> 
> # SharpDevelop 3.0.0.3800
> 
> Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "EpicEdit",
> "EpicEdit\EpicEdit.csproj", "{67D2F08E-7925-4E20-A9E9-07D4CAA24B20}"
> 
> EndProject
> 
> Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "EpicEditTests",
> "EpicEditTests\EpicEditTests.csproj",
> "D1C35FCD-7506-4247-9396-4FEAFEC21526"
> 
> EndProject
> 
> Global
> 
> 	GlobalSection(SolutionConfigurationPlatforms) = preSolution
> 
> 		Debug|Any CPU = Debug|Any CPU
> 
> 		Release|Any CPU = Release|Any CPU
> 
> 	EndGlobalSection
> 
> 	GlobalSection(ProjectConfigurationPlatforms) = postSolution
> 
> 		{67D2F08E-7925-4E20-A9E9-07D4CAA24B20}.Debug|Any CPU.ActiveCfg =
> Debug|Any CPU
> 
> 		{67D2F08E-7925-4E20-A9E9-07D4CAA24B20}.Debug|Any CPU.Build.0 = Debug|Any
> CPU
> 
> 		{67D2F08E-7925-4E20-A9E9-07D4CAA24B20}.Release|Any CPU.ActiveCfg =
> Release|Any CPU
> 
> 		{67D2F08E-7925-4E20-A9E9-07D4CAA24B20}.Release|Any CPU.Build.0 =
> Release|Any CPU
> 
> 		D1C35FCD-7506-4247-9396-4FEAFEC21526.Debug|Any CPU.Build.0 = Debug|Any
> CPU
> 
> 		D1C35FCD-7506-4247-9396-4FEAFEC21526.Debug|Any CPU.ActiveCfg = Debug|Any
> CPU
> 
> 		D1C35FCD-7506-4247-9396-4FEAFEC21526.Release|Any CPU.Build.0 =
> Release|Any CPU
> 
> 		D1C35FCD-7506-4247-9396-4FEAFEC21526.Release|Any CPU.ActiveCfg =
> Release|Any CPU
> 
> 	EndGlobalSection
> 
> 	GlobalSection(SolutionProperties) = preSolution
> 
> 		HideSolutionNode = FALSE
> 
> 	EndGlobalSection
> 
> EndGlobal
> 
> 
> 
> Hmmm, thinking about it just now... Maybe the problem doesn't lie in the
> sln file. My second project doesn't have an assembly file, could that be
> the reason? Should all projects have an assembly file attached to them? I
> didn't bother, since the first project is the whole app itself, while the
> second one is just for unit testing.
> 
> By the way, is MonoDevelop 2.0 actually out? I'm on openSUSE, just
> installed an update, and it doesn't say "Beta" anymore... No words on the
> official site, though.
> 

-- 
View this message in context: http://www.nabble.com/Problem-with-multi-project-solution-tp22716894p22732218.html
Sent from the Mono - MonoDevelop IDE mailing list archive at Nabble.com.