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
Related
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
I know this is a strange situation, but consider a situation where two programmers are working on one project. One programmer is working on a database driven website in ASP.NET in Visual Studio 2012, while other programmer is working on Visual Studio 2008 on another part of the same database driven ASP.NET website.
What in your opinion is the best way to integrate the two codes?
PS: Downvoters please explain in comments, before downvoting. :-)
Make the second developer update his VS copy to 2012. If you are working with two disparate versions of VS, you will very simply be unable to have either developer work on any part of the codebase that was built with (or upgraded to) the other version.
Once everyone's working on the same platform, and thus can load and build the same solution, project and source code files without error, "integrating" the two codebases becomes rather trivial. Of course, the conversion process may not be so trivial.
My first step would be to ensure that a reliable backup of the entire codebase has been taken; you can copy the flat files to a file store, or more reliably you can use a centralized VCS like Subversion to make sure a single authoritative copy of the codebase as-is exists and can be easily retrieved. Then, while the 2008 dev is updating his machine to 2012, have the 2012 developer pull the whole codebase and load whatever solution the 2008 dev had been working in, and run through the conversion wizard. This wizard will update the XML behind the project and solution files to support features of the new IDE version.
If you absolutely positively cannot get both devs onto the same IDE version, there's still hope. Have the 2012 developer open a new solution file in his copy, and pull in the 2008 projects. If VS asks to convert them, you're SOL; the other dev will HAVE to upgrade, or the 2012 dev will have to revert. But, if the IDE doesn't complain, the 2012 dev can save the new solution under a different name and work with the projects and their source code using that solution file, while the 2008 dev can continue to use the original one. Understand that as long as this state of affairs continues, the 2012 dev cannot use any features of C# 4.0/4.5, such as dynamic types, covariance/contravariance keywords, optional parameters/named arguments, async/await keywords, etc cannot be used in any source code that must remain usable by the 2008 dev. Language-wise, the 2012 developer is limited to C# 3.0, and the .NET Framework 3.5. This does not solve the problem of the 2008 dev not having access to code written from scratch by the 2012 dev in projects created by that IDE; he simply must upgrade to work in these parts of the codebase.
I understand that using the WebMatrix is easier as the tool seems more focused towards ASP.NET. However, I was curious to know through if it is possible to also create the same ASP.NET files using just Visual Studio. Would using the WebMatrix be a good start for understanding how to create web applications. Visual Basic can create applications that will run on your computer also right?
WebMatrix is a do it all package with Express IIS, Visual Studio is an IDE developed towards the .Net framework. Basically Webmatrix is specialized towards Web Development and Visual Studio is a powerhouse package that has a Web development aspect. That is the basics of it. Hopefully someone has a much more in depth answer but to tell you the truth, this is easily re-searchable via Google.
Webmatrix = web application focus;
Visual Studio = you decide the application focus;
If you want to do only Web and feel that Visual Studio is too much for the kind of project you want to do, which is true in a lot of cases, then I would suggest just using Web Matrix. As your project grows, however, you will soon find yourself in Visual Studio simply because it has more power and reach to build more complex systems.
I generally spin up a Web Matrix app if I want a quick catch all solution (kind of like MAMP or XAMMP) to test a small application, or play around with sql.
As far as I understand the major difference is Webmatrix supports PHP and node.js.
You can read more here :
http://www.microsoft.com/web/platform/tools.aspx
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.
I'm coming from the open source world, and interested in giving ASP.NET a spin. But I'm having a little trouble separating the tools from the platform itself in regards to the licensing. I've downloaded Visual Web Developer 2008 Express, but not sure how different this is from one of the full-featured Visual Studio licenses -- and whether or not my Express license will prevent me from using all the features of ASP.NET.
Is a Visual Studio license just an IDE, or does it include pieces of .NET not available to the Express license? What about the other tools like IIS and SQL Server?
Thanks.
All of .net is available in the .net SDK, so in theory you will not need Visual Studio at all.
Now, there are some things that Express will not do. For example, the Database Designer is not very comprehensive and adding different remote databases is not or only very hardly possible. Still, in code you can connect to everything.
There is also no Remote Debugger, no support for creating Setup Files (well, that does not apply to ASP.net anyway), no real Publish Web Site Feature (although that can be added manually as it's just a Frontend for a SDK tool), no integrated Unit testing (and Microsoft loves to threaten people who add it), etc.
For a full comparison, see here:
Visual Studio 2008 Editions
But as said: Functionality of .net is all in the SDK, Visual Studio is just making it a bit easier to work with.
Visual Studio is just an IDE, you can do all your .NET development with the SDK and notepad if you choose. In fact there is something to be said for learning it that way so you understand better how the pieces fit together!
Microsoft have a version comparison matrix available so you can see exactly what is included each version.
IIS is a Windows component and considered part of the OS, there is nothing else to buy.
SQL Server comes in many flavours, SQL EXpress is free to use and whilst limited compared to the versions you pay for, it is more than enough to get started with ASP.Net
Visual Studio is the IDE and does not include the platform.
IIS and SQL Server are separate products. IIS is available as part of the windows install and the version is different depending on what version of Windows you are using.
SQL Server also has an express product which is not as full featured as the Full versions of SQL Server, yet it is still rather valuable and useful especially for learning purposes.
You can learn a lot from the free tutorials found on asp.net.
Visual Studio is just the IDE. You could theoretically create every file in Notepad and compile manually with just the .net framework.
IIS is an operating system feature, and SQL Server has different flavors with different capabilites.
SharpDevelop is a Open Source IDE for C# and VB.net