Awesome ! It works like a charm ! Thanks !

Ah ha! That is indeed the issue. I found the cached files in %localAppData%\Nuget\Cache. Thanks for the quick response!

I think I know why, The query shows either targetFramework='unsupported' (for update2 xproj) or targetFramework='DNX451' (for update1 xproj) I think it should use targetFramework='net451'

This is by design. The "Packages" listing page (/packages) lists the packages (and all the versions) stored on the local server, across all feeds. The "Feed" page (/feeds/FeedName) will show the aggregated view of packages on the local and remote servers, collapsing all the various versions into a single version.

I understand... you want the ProGet web server to host/serve the icon files themselves... It's very unlikely we will implement an image/file hosting feature. There are plenty of image/file hosting servers out there, or you could just use a basic IIS site to serve files from disk. Note that, on the NuGet roadmap, there is a feature to store icons in the package, like ProGet's universal packages does, using package://myicon.png; this would simplify things quite a bit.

ProGet 4.0.11 is now available, which includes support for scoped packages. You can get it from the downloads page: http://inedo.com/proget/download

Thanks Andy ..server restart did the trick...cheers!!

Hi Alana, Thanks for the comprehensive answer. Looks like things are still quite away off then. It's a pity mono is not more stable right now, hopefully Microsoft will put in some investment, but it looks like SQL Server is not going to be available until for at least another year.

Thanks, this works :)

This has been logged in our issue tracker - it will be fixed in the next release, which will be v4.0.11. We should have that available early next week. It looks like this was just an oversight on our part.

I'm afraid we don't have any tutorials for this ourselves, but there a lot of third-party tutorails out there for using mvn. Here's one that might be helpful, directly from maven project:https://maven.apache.org/guides/mini/guide-3rd-party-jars-remote.html

With any versions of ProGet – from free to Enterprise – you’ll be able to access the repositories but scaling down from Enterprise to basic, or basic to free , you'll lose access to license filtering, feed-level user privileges, and other benefits that many users have come to enjoy, depend on, and take advantage of throughout their use of enterprise or basic ProGet. Very rare are there cases folks want to lose those features but if it's necessary, your team will still be able to access the repositories. Take a look at the full break-down of features and benefits per version here: http://inedo.com/proget/pricing/features-by-edition

Whoops, updated! It's http://inedo.com/proget/roadmap

Is this feature now available? Where could I find documentation to this?

This should be fixed in the 5.0 beta, which we will probably have available for download this week. Basically, we are dropping those _WRK, _SRC, directories entirely from OtterScript plans in favor of something a little easier to reason about. We'll have more information about this behavior in an article soon.

Alright, well I did manage to make it work using IIS so at least there is a workaround, however since that was the only thing on that server that needed IIS it's too bad that I had to install and configure it only for that purpose. Thanks.

Thanks for letting us know; this is something we want to work very consistently in 5.0, so it's possible it's working half the "old" way (OtterScript plan wrapping an old action), and half the new way (a new "operation").

Thanks for the help... in the end I found I needed to install Microsoft Visual Studio 2012 Agents on the build server. The project was then able to build successfully.

I bumped into this issue as well. It turns out if you wanna use existing local SQL server, you need to add an account "NT AUTHORITY\NETWORK SERVICE" to your SQL database. To be clear, this account is added to ProGet database during installation but it didn't mark as "Public" in server role.

Yes, but it's not "officially" scheduled as BuildMaster v5 is the top priority at the moment. Here is the roadmap for reference: http://inedo.com/proget/roadmap