![\"Smile\"](\"https:\/\/www.cloudidentity.com\/blog\/wp-content\/uploads\/2014\/07\/wlEmoticon-smile.png\")
) through this GitHub repo<\/a><\/li>\n\nYou will need to submit a Contributor License Agreement<\/a> form before submitting your pull request. This needs to only be done once for any Microsoft Open Technologies OSS project. Download the Contributor License Agreement (CLA). Please fill in, sign, scan and email it to msopentech-cla@microsoft.com<\/a>.<\/li>\n
- \n
- In fact, you\u2019ll be able to grab nightly builds directly from MyGet! see below<\/li>\n<\/ul>\n<\/li>\n
- Configure Visual Studio to get ADAL symbols and step into ADAL\u2019s source while debugging your own apps!<\/li>\n<\/ul>\n
Note that we will keep releasing new NuGet versions (stable and prerelease) at the usual location<\/a>, with the usual support policies \u2013 the code is an additional way for you to get even more value from ADAL and does not substitute our usual release cycle.<\/p>\n
As you might infer from the number of exclamation points, I am pretty excited about this!
\nAll of the above points are pretty self-explanatory, but the MyGet and VS configuration for vacuuming down the library symbols require a bit more guidance: see the instructions below.<\/p>\nConfiguring Visual Studio 2013 to Access AAD\u2019s MyGet Feed<\/h2>\n
Our collaboration with the ASP.NET team on the OWIN middleware components for OpenId Connect made us experience first hand how convenient it is to have a MyGet feed where we can dump nightly builds and use it as a collaboration touch point as we refine our software. Hence, we decided to extend those benefits to ADAL itself.
\nTo configure the AAD MyGet feed in VS 2013:<\/p>\n- \n
- Go to Solution Explorer->[project node]-> Manage NuGet Packages\u2026->Settings.<\/li>\n
- Hit the \u2018+\u2019 button on the top right corner<\/li>\n
- In the Name field, enter something to the effect of \u201cAAD Nightly\u201d<\/li>\n
- In the Source field, enter\u00a0 http:\/\/www.myget.org\/f\/azureadwebstacknightly\/<\/a><\/li>\n
- Hit \u2018Update\u2019<\/li>\n
- Hit OK<\/li>\n<\/ul>\n
\u2026and voila\u2019! From now on you can get the absolute freshest (and totally unsupported, BTW
) work-in-progress ADAL build.<\/p>\nRemember, for official previews and stable releases keep referring to the NuGet.org feed.<\/p>\n
Configuring Visual Studio to Load ADAL Symbols<\/h2>\n
In my opinion, this is one of the coolest VS + NuGet features for open source projects. How many times have you wished to unpack that mysterious error and get to the bottom of what exactly <\/em>is failing in that oh-so-handy-but-oh-so-black-box library you\u2019re using? Well, now with ADAL you can! It just requires a bit of configuration.<\/p>\n
You basically need to follow the \u201crecommended configuration\u201d section of this page<\/a>.
\nHere there\u2019s how my debugger options look like after I have done so:<\/p>\n
![\"image\"](\"https:\/\/www.cloudidentity.com\/blog\/wp-content\/uploads\/2014\/07\/image_thumb.png\" "\\"image\\"")
<\/a><\/p>\n![\"image\"](\"https:\/\/www.cloudidentity.com\/blog\/wp-content\/uploads\/2014\/07\/image_thumb1.png\" "\\"image\\"")
<\/a><\/p>\n