Posts

Showing posts with the label Visual Studio

Increase your API usability by teaming up NuGet and Visual Studio

Image
Tags van Technorati: NuGet In my previous post I described a way to use NuGet for packaging libraries, often used in projects. This post is an addendum to my post ‘enter 2014 with NuGet’ look at the additional features possible. In this post i’m looking into Visual Studio features (project templates) and the NuGet package feature PowerShell . I’ve been working on an API (see my next posts, Service Bus Series - ‘the case for service bus’), and during the development I wanted to make sure that explaining the API to another co-worker was a nicer experience than just going through the code. To ensure that the developers could easily connect and understand the usage of the API, I decided to create sample projects using templates. Templates are a great way to provide the user with a sample project from within Visual Studio. I wanted more… and with the features available in NuGet packages, i’ve found a way that worked for my scenario. I’ve been using the principles; Each project in Visu...

Add project reference? Enter 2014….Using NuGet for packaging projects and dependencies

Image
  [UPDATE] Sample solution available on OneDrive ( https://onedrive.live.com/?cid=5eaaef40eefdaddb&id=5EAAEF40EEFDADDB%21109 ) A solution consists of projects, projects uses components, components are of a specific version, changing the components thus requires a versioning strategy….which one are you using? All solutions which are architected into several tiers, have a form of layering with (which I hope) an abstraction of re-usable components. A project which is used to implement automated order approvals (AOA), with a requirement to implement logging, and retrieve something out of the database will likely have the minimum of 3 projects Solution AOA Project - AOA.Core Project - AOA.DataProject Project - Common.Logging Let’s assume, that the Logging library is also used by another solution: BOB Solution BOB Project – BOB.Core Project – BOB DataProject Project - Common.Logging When the requirements of logging change, and the project BOB needs a specific change d...

XLang – Debugging BizTalk from within VS.Net

Image
When developing Orchestrations, you are using a visual designer, which will in effect generate XLang which is handled by the BizTalk Xlang engine. Although the Xlang engine has its own language XLang, it does support some shapes (Expression shapes, Delay) which are compatible with C#. It’s also possible to call .Net assemblies from an Atomic scope, and debug these following the steps; described in this post: Debugging .Net ): Build the external C# library project Add it to the GAC Restart the Host Instance Attach the debugger to the Host instance All great stuff, additionally, you can use the Orchestration debugger ( Orchestration debugger ) which connects to the XLang scheduler, all fine and dandy. When you however, have an orchestration that directly fails, with an error you cannot comprehend, or tracking is disabled, you’re not so happy. Tracking is performed at the persistence points ( Persistence points ). An Expression shape (which does not lead to a...

Visual Studio 2012–changes necessary to start doing your work

Image
  Disclaimer: This post does not take any company security policies into account, actions suggested are merely provided to support getting things done as a developer…having said that What’s the first thing you probably will encounter when (implicitly) converting an existing solutions from an older Visual studio… Security You must ensure that you can do your work….especially when converting solutions from an older Visual studio version, it’s very annoying that solution will be migrated but are not able to change properties in projects etc. Example of Zen demoter…..Changing the read-only bit from solutions (e.g. downloaded sourcecode); How to start you work…and increase your Zen level? Change User Access Control Note: Personal judgement is necessary to determine whether this should be done! Run Visual Studio as an administrator You can do this by changing a property in the visual studio shortcut. Now you can start doing your work