I figured out the problem was with the cloud service name. I was including the build number in the name and it just so happens that build number includes the {Major}.{Minor} numbers. The period was ultimately throwing it off. If you want to include the build number, then you have to use a url friendly number.

are you a programmer? if not no need to ilsatnl it.If you are, MSDN (Microsoft Developer Network) as the word suggests is a developer centre where you can find Softwares developed by microsoft. They provide technical support and help developers to develop their client softwares using Microsoft developed softwares (visual studio,asp.net etc).Developers also can help develop the software to be more efficient.If you are a programmer you can subscribe to MSDN to get developer tool to enhance you skills.MS Windows SDK (software development kit) contains all tools, libraries, sample files to work upon, so that you can independently develop Applications for yourself hitherto for microsoft as well. you can develop applications for Operating system. for eg .their comes a SDK to develop Windows narrator under dot net framework.

Hey, This is great news! Thanks for getting this sorted out so quickly! Gary

We uncovered the cases in which it might lock... this should be addressed in ProGet 2.1.2 (released today).

Have you done any perf. testing beweetn sqlite and sqlce 4? I run a website with very fast response times using sqlite but the write operations are defintely blocking to all readers. the site is about 80% read and 20% write. I was contemplating moving over to sqlce as our number of visitors have increased - lack of support for windows 8 has me a bit worried.

Great, many thanks for your support!

This is likely a subversion/workstation configuration problem. Sometimes two versions of Svn.exe -- the one you installed (like tortoise svn) and the one built-in to the extension -- cause conflicting configuration. Try to change the provider configuration (Admin > Source Control) to point to your own svn.exe instead of the built-in client. Also, try to change the option to use SVN UPDATE instead of EXPORT for this provider.

There's no specific error message, aside from the SQL error that's being thrown. Since you have both on the same server, perhaps it'd be best to have a single SQL Server instance (SQL Express), and have the BuildMaster and ProGet databases hosted in that server.

Hi Dave, There is new release of the Linux extension (v3.12) that will resolve this issue. Best, -Steve

Thank you Alex, as you suggested, the issue has been solved increasing the maximum allowed content length in IIS.

Thanks for the info. In regard to switching the exe.. should I be able to save the change from using the built in exe to a standard one without hitting the "Test Connection" button? When I try switching to an external git.exe and click the "Save" button, I can open the provider properties back up and the "Use Standard Git Client" option is unchecked again. Any other changes I make seem to save, just not changes to that option. The same thing happens when I create a totally new provider / source as well. I set it up to "Use Standard Git Client" and hit save then open the new connection up and it shows as unselected.

How much does the Boudoir photo session run? Do we need to pridvoe wardrobe changes? Any other information? I saw the thing on the front page about boudoir photography, does it still apply? I missed the June date.

Nevermind, the Build was already rejected.

Hi Dave, Can you send a screenshot of the action to support? Want to see the value of all the fields. Suspect it's not related to variables (they get replaced long before action code runs), more to masking, or something else... Thanks

Thanks, we will wait for the updated svn extension, and use the execute command line option in the mean time.

As it turns out this is a problem related specifically to the SVN extension and will require us to release a new version of the extension. We will have this out within the next few days. As a workaround, you can call the Execute Command Line action directly with the appropriate SVN checkout arguments in order to get the latest code.

Thanks for the work around. Saved us much headache!

Yes. Things appear to be working now.

The "IsAbsoluteLatestVersion" is an undocumented NuGet attribute (well... it's in the source code), and has a confusing relationship to the quasi-documented IsLatestVersion attribute. Long story short, these these attributes tend to behave differently in different versions of NuGet clients, and our changes to remain compatible with the upcoming NuGet 2.5 caused a regression. You shouldn't have to change anything in your packages -- just post here if you find issues and we'll figure it out.

Hi Matt, The BuildMaster agent doesn't need to be installed on the TFS Server itself; whatever server you're using as your build server (could be same server BuildMaster is installed on) should have the TFS Client (Team Explorer) installed. As for the agent error... the "IIS agent" is "SOAP Based" --- so you'd want to make sure to add a SOAP Based agent from the BuildMaster servers page. To test that IIS agent is installed, you can do http://localhost:81/agent.asmx -- if that page shows up, the the agent is configured in IIS correctly.