I've recently started playing around with ASP.NET and I was just about to connect to a database using LINQ, when I realised that you have to change a bunch of stuff in the project first if you created a normal web site project in Visual Studio 2008.
All the information about LINQed projects in VS2008 that I have found start directly from scratch with a completely new web site. What modifications do I have to make to my project to be able to make use of LINQ?
I think that your question can be answered by viewing this post on stackoverflow.com.
In short your application will need to have access to System.Linq which comes from the .NET 3.5 framework. If your application is currently using .NET 2.0, it is possible to hack a setup with the CTP packages for Linq prior to it being released with Visual Studio 2008, but you might find it hard when you push your application out to production to a hosting company because you will have to install .dll's into areas you generally don't have access too.
Good luck on your conversion to Linq.
Related
Which version of Visual Studio can be used to open a project which is built as ASP Web project
I have Community edition 2019 Does this support ASP projects?
I know these days no one is using ASP for building web apps The purpose is to maintain an existing ASP solution for a couple of more months 9If any bug fix requests from the client comes ) and start to build a new project using the latest version of Microsoft technologies
Visual Studio
Most versions of Visual Studio support editing Classic ASP code, couple of things to keep in mind though.
Frontpage Server Extensions is no longer supported, the best approach is to use a mapped drive or better yet store the code in source control (Git, SVN etc.) and work with the code locally (can bind to a local instance of IIS).
The IDE can be quite cumbersome for working with Classic ASP as it's designed for more modern technologies.
It also has sophisticated debugging through the IDE via the "Attach to process" which will work with Classic ASP running in IIS as long as the web application has been configured correctly for debugging. See How do you debug classic ASP?.
Visual Studio Code
Another option is Visual Studio Code which is a free IDE built on the principle of open source projects for cross-platform. It's becoming a popular free IDE for many developers rivalling the likes of Atom, Sublime etc.
It's lightweight and extensible through extensions, there are already some useful extensions for Classic ASP including this one;
Name: Classic ASP Syntaxes and Snippets
Description: Classic ASP Language Support and Snippets from tmBundle
Publisher: Jintae Joo
It also has built-in support for popular source control solutions like Git and more powerful available through the extension marketplace that is built into the IDE. If you do use Git would recommend installing the GitLens extension.
Every version of visual studio since I started with 2010 (was there something before it?) handles Classic ASP just fine. I'm on VS2019 right now.
I even have a project which is a combo Classic ASP, Webform, and MVC all in one project, with some session sharing, and I routinely code and debug in all. The only limitation is that when you debug, you have to choose whether you're debugging Managed code or "script".
With each I "attach to process" and choose which code I want to debug. Classic ASP debugging is fantastic, and I can't believe more people don't do it. I see basic questions on here which would easily be fixed with standard debugging techniques (settings breakpoints, evaluating variables).
The ONLY thing which isn't supported is code formatting inside <% %> blocks. If I ever get some time maybe I'll make an addon for it.
I created a ASP.net MVC 5 project in Visual Studio 2013, running in a Windows 8.1 Pro.
I've been ask to put my project on a SharePoint, but I don't quite know how it's done.
i tried creating a SharePoint project on my Visual Studio but it won't let me since I don't have SharePoint installed, and when I try to install SharePoint Foundation 2010 or 2013 it complains I don't have Windows Server.
How do I make my project work on a SharePoint?
So you want to put your project on sharepoint? Cool!
In your case you definetly want to get your own SharePoint environment. To develop Apps (or Add-ins as they are called today) you mainly use Client-side code and techniques. This also means that you need to handle the SharePoint resources with asyncronous programming. Its very powerful, But that is not what you are asking for.
I would set up an SharePoint 2013 Foundation environment since its free and will very much deliver the capabilities you are after. Keep in mind though that SharePoint is a HUGE system that requires some understanding to be utilized.
I made a blogpost a while back where i Installed Win Server 2012 R2 on a external disk, this example works with SharePoint if you just want to debug your project on a SharePoint server. Check it out here: http://bayerlein.se/install-windows-server-on-external-hdd-with-the-help-of-virtual-box/
This solution will of course also require that you install your development program in the same environment.
Good luck//Kodz
It really depends upon what you want to do. Do you need to create a provider hosted app with MVC for SharePoint 2013? In that case, you might succeed with including the necessary references and tooling code (but you still might lack the app manifest project). Technically your project won't run on SharePoint but uses the SharePoint API.
If you need to create an SharePoint solution package, you need a SharePoint development install (and as SharePoint doesn't install on all client OS, your best way is going virtual with a SharePoint development VM). Keep in mind that developing solution packages is a different kind of trade than developing for MVC, so start with a Pluralsite course or some other kind of training.
I think you can create a SharePoint app. You can use VS2015 with SP online so that you don't need to install SP locally. Create a trial o365 account and enable developer site on it. You can deploy your app on the developer site then. If you have developer site from you client instead of using sp online you can use that too.
Once your app works you can create package to deploy on the SharePoint environment.
I think right now, the best way for you would be signing up as Microsoft Office 365 Developer and having a trial of the 365 cloud where you can setup sharepoint 2013 site collection and also develop apps using their tool NAPA.
These days they are calling apps "SharePoint Add-ins"
NAPA and SharePoint Add-ins
I would also suggest you take a look at this article:
SharePoint 2013 Developing Apps vs. Solutions
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
I am responsible for supporting a relatively complex Website project written with .NET 3.5.
Previously I was using Web Deployment Project with Visual Studio 2010 to deploy this website but at the moment I have only access to Visual Studio 2013.
As far as I know, there is no longer such a tool to be used for deployment in Visual Studio 2013 and I do want to compile the code before deploying to the production server. As mentioned earlier, the project is a bit complex and this would not be easy to be converted to a Web Application.
Any idea?
Unless I missed it, unsure what the issue is - in VS2013, Publish is what you are looking for (either WebSite or Application).
What exactly do you mean by "none of the (vs 2013 publish) options worked"? What is/was the issue?
In one of your comments, you state you want to "pre-compile" (aka "don't want to upload .cs source files) and that's a setting in Publish.
You can Publish to your local file system: "Custom" -> File System:
This extension still exists for Visual Studio 2013: http://www.iis.net/downloads/microsoft/web-deploy
Little bit confused with the question because you are keep referring about website rather web application.
If you are looking to convert web site to web app then you need to follow this: http://msdn.microsoft.com/en-us/library/vstudio/aa983476(v=vs.100).aspx
Otherwise, if you are referring about the deployment project. Yes, it is no longer available.
I'd a very similar situation like you and Since 2013 I have stopped using any deployment project, instead I have started using Publish that creates a deployment package for you on a Network , FTP, Local Drive or even on Azure.
Here is a nice guide from Microsoft
http://msdn.microsoft.com/en-us/library/dd465323(v=vs.110).aspx
If you still want to go for Deployment Project, then you would need to go for "Installshield" limited edition,which is free (http://samirvaidya.blogspot.com.au/2013/11/how-to-enable-installshield-le-for.html).
http://msdn.microsoft.com/en-us/library/2kt85ked(v=vs.110).aspx
Doesn't Visual Studio generate all kinds of things when you build asp.net websites? I haven't used it in a while but back in webforms with a the dal and a bll, VS generated xml files and other things (don't remember what). And, while I technically could use notepad to fix it, VS seemed to be the only way to make sure things worked right.
How about today with MVC or something else asp.net? Am I tied to Visual Studio forever if I want to build websites? I liked in PHP that I can open up a file and it be simple to change things and it just works.
I am not knocking Visual Studio. It is a great product, but for those in my group that do not use it, it is a learning curve. Not asking for why asp.net is better than php or vice versa, just about visual studio.
EDIT: Is Visual Studio the BEST way to build asp.net projects?
You can use MonoDevelop, Webmatrix, Visual Studio Express but i suggest SharpDevelop, its open source.
sharpDevelop (short for SharpDevelop) is a free IDE for C#, VB.NET and Boo projects on Microsoft's .NET platform. It is open-source, and you can download both sourcecode and executables from this site. In addition, you can find the latest information and changes on #develop, as well as get in touch with the team in the forum.
More Information
SharpDevelop Website
MonoDevelop
Webmatrix
Visual Studio Express
No, you can build with MSBuild from command line, just simple msbuild.exe app.sln
You can also use MonoDevelop, which will run on Windows/Mac/Linux.
You could use Microsoft WebMatrix, which is free and aims to simplify the web development process. Another alternative is MonoDevelop, which is an open source IDE for multiple platforms.