I had convert my web application from visual studio 2003(framework 1.1) to visual studio 2010(framework 4.0).
After converted, I have pug-in Ajax 3.5 and test my web application.
The web application run well but the Ajax doesn't work.
There are not error appear in the application also.
What can I do in other to make the Ajax work???
Please advice...Thanks in advance.
Here is the solution:
just remove the script managers from the pages and add it again how it was, from the Visual Studio tool box.
close the browser and run it.
It should work fine.
Related
Is it possible to have the same application and debug client-side parts in the visual studio code and server-side parts in the visual studio? ASP.NET Core in particular
I actually figured it out by myself, so if anyone's wondering this is what you have to do:
VScode launch url should be the same as is on the visual studio, you should open client side project or wherever your files are. Vs should run on IIS server, that way you wont need to debug in visual studio in case you don't like debugging in chrome.
I have one web application in C# which is developed using Visual Studio 2010 and I want to convert or Migrate that web application in Visual Studio 2013 (C#).
Note:- Below listed things I used in my current Web Application using VS2010 (C#)
Asp.Net Server Controls.
ClassLibrary (.dll).
Web services.
Above Listed things I used in my current Web application which is in VS2010.
Now, My Question Is- What would be the major changes I would be facing if I am using all above listed Microsoft Technologies using C# and Migrate it to VS2013.
The biggest change for us was that Visual Studio Setup Project was depreciated in VS 2012, so we had to build new installers.
http://blogs.msdn.com/b/visualstudio/archive/2013/08/15/what-s-new-in-visual-studio-2013-and-installshield-limited-edition.aspx
Also, which version of .NET is you application? Keep in mind framework targeting for Visual Studios (basically if your application is .NET 3.5 SP 1 or newer you should be fine):
https://msdn.microsoft.com/en-us/vstudio/dn250998.aspx
The Web Services should also be okay, if you intend to keep creating web services instead of switching to WCF, you may want to look at this:
Create a asmx web service in C# using visual studio 2013
The thing we first noticed is VS2013 uses IIS Express 8.0, at the time our production web server was IIS 6 - we encountered, on numerous occasions a web.config setting working fine locally but forgot to add the IIS 6 equivalent.
For our web apps we kept targeting the same .Net framework and I can't recall any issues. For your reference our stack was Asp.Net MVC 4, EF 5 WebApi plus numerous NuGet packages. So we didn't have any asp.net server controls.
You may also want to ensure all your VS2010 plugins have a 2013 equivalent.
You shouldn't have any problem at all with the types of proyects you are using.
You could even open the solution with VS2013 and then open it back with VS2010 SP1 without any problem (as long as you don't switch the .NET framework to 4.5).
Starting from VS2012, Microsoft made changes to allow developers open a solution with older versions of VS (VS2010 SP1 being the oldest version that supports this). There ARE some proyect types that won't be compatible, but from the things you listed, you won't have any problems.
When you open the Solution with newest VS, it WILL make some changes, but you still will be able to open it with VS2010 SP1 (again, with some exceptions).
https://msdn.microsoft.com/en-us/library/hh266747.aspx
http://blogs.msdn.com/b/webdev/archive/2012/08/22/visual-studio-project-compatability-and-visualstudioversion.aspx
Anyway, my suggestion is, install VS2013 in a test machine and try it out. You can even create an Azure VM with VS2013 PreInstalled in minutes to try it out.
There is already available VS2015 preview, why not wait until it is released? (or use the preview)
https://www.visualstudio.com/en-us/downloads/visual-studio-2015-downloads-vs.aspx
as other said, it should not brake much
has anyone else dealt with this? My ultimate goal is to create a new empty web api project. I've been following tutorials and I've encountered the following issue:
My issue is that when I try to create a ASP.NET Web Application project in Visual Studio Pro 2012 I do not see that template as an option. I go to Installed --> Templates --> Visual C# --> Web
All I see is ASP.NET Empty Web Application. So I selected that and then expected the ASP.Net project window to pop up so that I could select "Web Api". However, that dialog never opened.
Does anyone know how/where I can get the ASP.NET Web Application template?
I came across your question as I had the same problem. When I first installed Visual Studio I didn't tick the box to install the Web Components. Here is how I solved the issue:
Close all your instances of Visual Studio.
Run the Visual Studio Installer (I found mine in the Downloads folder still and was named "vs_professional.exe").
For VS 2013 a grey window appears similar to when first installing VS.
When prompted select "Modify" from the list of options.
Tick the list item which I think was named "Web Development" or something similar.
Click update.
Once the installer has finished running launch Visual Studio.
When selecting New Project in Visual Studio I can now see the required templates.
Try to select Framework 4.5.
The Framework 4.0 don't have :)
Jorge Rocha
If you have ASP.NET MVC 4 Web Application as an option under Web when you select it as a new project the project window pops up and you will be able to select Web API.
kale909's solution worked for me. I just added pics here to make it more clear:
then here:
I have created a website using Visual Studio 2012. It is working just fine. The problem is I have to deploy it on a server that has .Net Framework 2.0 only. So I created another website using Visual Studio 2012 and set its version to 2.0. After copying the code of just a single page I tried to run it. But I am getting the errors "Unknown server tag asp:ScriptManager" and "Unknown server tag asp:UpdatePanel". I need them both as I have to use PageMethods in my page. How can I create a .Net Framework 2.0 website with ScriptManager and UpdatePanel without any error? Thanks in advance.
You didn't have to recreate your project. Go to the project settings, application, then change the "Target Framework".
To clearly answer your question, the answer is : you can't.
As Jamie Keeling suggested, Script Manager and Update Panel came with .Net Framework version 3.5.
You will have to find other components or some kind of workaround.
You might have to install ASP.NET 2.0 AJAX Extensions 1.0 if you are planning to use scriptmanager and update panel in .NET 2.0. Prior to .NET 3.5, Ajax was available as a separate library.
I am using Visual Studio 2012. I have been developing on a legacy web site that uses .NET 2.0. It is configured on my local machine using IIS with an application pool set for .NET 2.0. I am able to open this web site from Visual Studio using File-Open-Web Site....no problem. This is a web site, not a compiled web application.
I just changed my application pool to .NET 4.0. My web site runs fine.
However, when I select File-Open-Web Site in Visual Studio, I get an error that says:
The site "...." is currently configured for use with a newer version of ASP.NET (4.0). This project is targeting ASP.NET 2.0; if not configured some features with the tool may not render correctly. Would you like the site to be configured for user with ASP.NET 2.0?
I can click "No" and attach to and debug the application no problem.
I have no SLN, SUO, CSPROJ, or USER files anywhere in the web site or in My Documents. I have deleted the contents of my web.config file so that it is empty. I still continue to get this message every time I open the web site.
Where is this message coming from?
Why does Visual Studio think that the web site is configured for .NET 2.0?
This is something local to my machine.
Other developers in the company have upgraded their application pool to 4.0 and do not see this message when opening the web site from Visual Studio.
While you may have upgraded your solution to be opened by Visual Studio 2012, you haven't changed the targeted .NET runtime.
To target something other then the .NET 2.0 runtime you need to change the target in the project properties.
See the following for a complete explanation.