Posts

Showing posts from March, 2014

Creating NuGet packages from a solution

Image
Alternate title: Packaging multiple projects into one NuGet package [Updated Thursday, March 13th, 2014: Added Troubleshooting] Background For a recent client project, to make it easier for my developers to create certain types of projects, I created specialized NuGet packages that contained the most commonly referenced infrastructure pieces that they would need. For example, if they were to create a portable  Application Service  component, they would want to reference the shared Foundation library, followed by a Application Services Foundation library and some Common Data Types. I also knew that they would be dependent on a number of NuGet packages, prominently the Microsoft.Bcl package (which, in turn, references Microsoft.Bcl.Build). Let's walk through how this is done! To create a singular NuGet package containing all these references, create a new, Blank Visual Studio solution, add a Solution Folder called "Package Source" and a Portable Class Library Pr

Debugging session ended.

Image
I've been involved in some Xamarin development of late (which is evident from the other blog I've been writing at - monodeveloper.org ). I recently ran across a tedious issue at a client's and I thought I'd share the solution with you, dear reader, so that you don't have to waste nearly as much time as I had to. Scenario: You have built an iOS application in Visual Studio. It might've worked before, it builds now, but nothing ... happens. Visual Studio says "Debugging session started", followed by "Debugging session ended". Error list says nothing. Output says nothing. Hell, not even the "Mac Server Log" spits out anything useful. Everything seems peachy here So what do we do? As it turns out, there are more logs we have access to! On the Mac build server, we can access the build process' logs through the Console app (CMD+Space "console"): Aha! That's  the issue! As you can see from the screenshot