[Minor] Issue with project opening

[ghost]

At first, i tried to use a "clone to esctop" button, but github app returned me an error like this: http://clip2net.com/s/5nynJB I assume, something is wrong with settings, because i definitely have internet connection :)

Then, i tried "download zip", but after opening, i saw that wp7 projects are not loaded. I removed and added project again (Toolkit WP7) , and got this error: http://clip2net.com/s/5nyrdW

[pedrolamas]

That's due to some missing packages when a new repo is just cloned. Rebuilding the WP8 projects should make NuGet install the missing packages, so try rebuilding them, then close the solution and reopen it and check again.

[ghost]

Well.. tried to rebuild whole solution, got this: http://clip2net.com/s/5nIfAK After that, i reopened project, got pretty the same result.

[pedrolamas]

The "MSTestFramework" error tells me you're Visual Studio is not up to date! Download and install the Visual Studio 2012 Update 3 here.

[ghost]

Ok, would do it. I guess, it would be nice to mention that on the front page. :)

[ghost]

Well.. after updating and rebuilding, "packages" folder appeared (StyleCop.MSBuild.4.7.44.1 and WPtoolkit.4.2012.10.30 are inside), but i'm still having the same problems with opening wp7 projects.

[pedrolamas]

Does your Visual Studio have NuGet package manager installed? Did you activate the package restore option in the settings? I'd assumed these are common development settings in any Visual Studio installation (along with keeping it up to date) but I guess in the end you're right and I should have pointed this all out in the front page! :)

[ghost]

1) Yep, sure. 2) Hm.. i looked here: // Tools-> Options-> Package Manager-> General : "Package Restore : Allow NuGet to download missing packages during build". I had that checkbox (i didnt do it manually before, so it is checked by default).

I guess, it would be nice to have some basic instructions, at least for those, who are looking for sources, "just in case" (c). :)

[xperiandri]

So, the problem is that WP7 projects depend on BCL.Build But as long as Visual Studio can't load them it can't find that they depend on that package :) Recursive dependency

So, @PedroLamas you can add BCL.Build to source control (at least critical files) or update BCL.Build dependency to the latest version please, so we can install it from NuGet repository.

[jeffwilcox]

Isn't there a way to enable msbuild to pull in nuget packages that it needs?

Sent from my Windows Phone

---

From: Andrii Chebukinmailto:notifications@github.com Sent: ‎7/‎22/‎2013 12:51 PM To: Cimbalino/Cimbalino-Phone-Toolkitmailto:Cimbalino-Phone-Toolkit@noreply.github.com Subject: Re: [Cimbalino-Phone-Toolkit] [Minor] Issue with project opening (#16)

So, the problem is that WP7 projects depend on BCL.Build But as long as Visual Studio can't load them it can't find that they depend on that package :) Recursive dependency

So, @PedroLamas you can add BCL.Build to source control (at least critical files) or update BCL.Build dependency to the latest version please, so we can install it from NuGet repository.

---

Reply to this email directly or view it on GitHub: https://github.com/Cimbalino/Cimbalino-Phone-Toolkit/issues/16#issuecomment-21370699

[pedrolamas]

I don't see the point in adding the NuGet packages directly, all that it's needed it to pre-install the packages, so... I've added a "setup" option to the build process!

Just open a PowerShell window, enter the "build" folder, and run

.\psake.ps1 setup

[pedrolamas]

@jeffwilcox yep, but given I already use PowerShell to build and create the packages, I think it's also a nice way to setup the environment... also, I think that using PowerShell seems a bit more "future prone" for situations like this!

[jeffwilcox]

Sounds like the right solution, cool.

[pedrolamas]

@VeTaLNearga have you been able to open the project using the indicated solution?

[pedrolamas]

Closing this as not further contact has been established!

[rikkit]

For what it's worth Pedro i had the same problem as the op and your powershell fixed it.