We are in the process of setting up new infrastructure for our dev team, one of the things that we are doing is setting up an internal nuget server.
We have followed the guide here https://docs.nuget.org/create/hosting-your-own-nuget-feeds and everything is working. However some of our dev team still rely on Visual studio 2012 which does not seem to work with this server, I assume that this is because the API has moved on and the client built into 2012 cannot connect to the server.
My question is what is the best way to deal with this, we have a mix of VS2012 and 2015 in use, It occurs to me that we could set up another server using an older version of the nuget server and point it at the same packages directory, however I am not convinced that this is the correct course of action?
If you need to support NuGet v2 clients, such as Visual Studio 2012 then you need to provide a NuGet v2 server. NuGet v2 clients cannot use a NuGet v3 server if it only provides the index.json endpoint.
Options are:
Use an older version of NuGet.Server that supports NuGet v2.
Use a file share instead of a server.
Use some other server instead that provides a NuGet v2 server, such as MyGet, or one that you can host locally such as Team City.
Update to Visual Studio 2015.
Related
I'm migrating from VS2015 to VS2017, and updating a repo's solutions to be able to be compatible with VS2017. In the process, I'm also updating the Azure SDK version from 2.7 to 3.0.
I'm setting up a fresh dev environment, and installed Azure SDK 3.0 via VS2017's Azure development workload.
When I opened the solution file in the repo, I got one notice per cloud service project that its Microsoft Azure Tools version was getting upgraded from 2.7 to 2.9...
...and the ProductVersion tag in the corresponding .csproj files was updated from 2.7 to 2.9.
Questions:
Why wasn't this updated to 3.0?
Is there anyway for me to update it
to 3.0 without manually editing the csproj file? I don't see an
option to do so in Properties when I right click the cloud service
projects in Solution Explorer.
Is there some reason I shouldn't be
doing this?
"Microsoft Azure Tools - v2.9" mentioned in your screenshot is just a little misleading.
Underlying reason is that Microsoft hasn't really changed the version number of most components as part of 3.0 SDK release. Even the binaries get installed in the same folder as 2.9.
Good news is that you don't need to do anything special apart from converting the project to target latest version, which you're already getting prompted for.
So once you do convert your project as per the prompt, you're essentially working with SDK 3.0, even though version string says v2.9, because as the links explain, most of the components haven't changed major version number as part of SDK 3.0 version (when comparing with 2.9)
Here are some of the links which talk about this -
Azure SDK for .NET 3.0 Release Summary
No breaking changes to the Azure SDK 3.0 have been introduced in this
release. There is also no upgrade process needed to leverage this SDK
with existing Cloud Service projects. To allow use of the Azure SDK
3.0 without requiring an upgrade process, Azure SDK 3.0 installs to the same directories as Azure SDK 2.9. Most the components did not
change the major version from 2.9 but instead just updated the build
number.
Visual Studio 2017 latest installer does not install Azure SDK 3.0
In this link look at the response from Devin Breshears - MSFT
Azure 3.0 SDK Install Weirdness
An independent blog talking about the same issue.
After I updated VS2015 yesterday and I cannot run my project (singla page app) anymore... Visual Studio says: Unable to connect to IIS express
I am using Solution DNX SDK version: 1.0.0-beta5
And my project.json is:
My references:
So everything should be ok ??
What am I doing wrong ?
BR
You have to understand that direct IIS hosting is no longer supported (and probably never will be again)! This is a decision by the ASP.Net team at Microsoft to completely concentrate on the kestrel server which is anyway required for Mac/Linux/Docker. By concentrating on one server the quality rises for everyone. Like Node, Kestrel recommends to use a reverse proxy in front of it. For that you can use your IIS/nginx/Apache.
I would urgently recommend you setup your project with RC1 and change to kestrel with HTTPPlatformHandler (in VS2015 Update 1 that works transparently with IIS Express for you). Beta5 is very outdated for many things.
It might be possible that your project could take a few hours before being able to run again.
First, you skipped beta6, beta7, beta8 and we are now at RC1.
Check which runtime you can use in Visual Studio and make sure you run with the latest one.
Once this is done, ensure that all your dependencies branded beta5 are renamed to the proper version that is in your Visual Studio. Some packages may have been removed, classes moved and many other things.
Check here for breaking changes:
Changes in beta6
Changes in beta7
Changes in beta8
Changes in rc1
According to this article some support for older versions of Azure are going away:
https://azure.microsoft.com/en-us/blog/microsoft-azure-storage-service-version-removal/
We have a vs2008 application that is uploading files to Azure. {Using Azure 1.2 (for VS2008) - Microsoft.WindowsAzure.StorageClient v1.0.0 - Runtime v2.0.50727}.
We can't have this break since we are using this in production.
I need to know if there is a clear way to know if this is going to stop working.
I would really like to know if there is a way to upgrade the vs2008 project to use a compatible version of the StorageClient without migrating the project to vs2015.
Your version of the library should still be supported after the service removal. You can confirm which version of the service you are hitting by running requests through Fiddler and checking the x-ms-version. As you can see in the most recent post regarding our service deprecation, we are only removing version 2009-07-17 and older as of August 1, 2016.
How to use TypeScript for Mobile Services scripts (with node.js backend)?
Is there a definition file for Mobile Services? (on the server, not on the client!)
And how about the tooling?
Sure, I can open the scripts in Visual Studio 2013 via the Azure node in the Server Explorer, but than they are not part of a Visual Studio solution. How to add a definition file via NuGet in that case?
If you enable source control on your mobile service, you can upload your scripts via git. This would enable a workflow where you write your scripts in TS, run the compiler to output JS, and you commit the generated js files to your repository and push them to the server.
Unfortunately I do not have any advice regarding tooling support.
You can use the TypeScript definition here: https://www.nuget.org/packages/azure-mobile-services-client.TypeScript.DefinitelyTyped
I watched EF4.1 and n-tier application video for Julie Lerman,
she added a new ASP.NET Empty Web Application project in the solution (VS 2010). After that she added a new item, WCF Data Service.
I can not find this item in Visual Studio Express 2012 for Web. Could you please help me? Is this a limitation in the express 2012 version?
Here is an image of what I can see in the Add New Item form
I can't post answer my question, so:
I should intall "WCF Data Services 5.2 RTM Tools Installer"
More details on WCF Data services blog.
Thank you.
Yes, you need to install "WCF Data Services 5.2 RTM tools installer". For the VS pro and ultimate versions, we chain in the installer for "WCF data Services - 5.0". For the express editions, customers need to install the version they need.
One thing to note - even in Pro/Ultimate editions, the version that gets installed is 5.0. For newer features (like the new JSON format), customers will require to install the latest bits so that they can get all the new code generation features.
Thanks
Pratik