We have graphic designers that work on the "look & feel" of our web applications. They typically work with HTML, CSS & images. How can we set up a designer's development environment to work with TFS, Asp.Net MVC 3 Razor Views? What would be the best workflow for them?
We want them to be able to check out the views / css from TFS, edit them, view the results and then check back into TFS.
How can they see their changes to views & css if they don't have the full Visual Studio or IIS or IIS Express?
Should we periodically deploy a web application to a web server for them to work on?
I believe you can download Visual Web Developer Express for free. Once they get that, they can run the project locally (assuming they have access to the database if there is one).
I'm not sure if the TFS plugin is free, if it is then they can work with source control.
Related
I have a lot to do with nodes and edges. I need to pull from a file/store, draw the graph, and allow interaction to apply filters or rendering styles. Graph Dracula seems perfect.
Unfortunately, I have only the basic understanding of HTML, JavaScript. I feel like AngularJS or the MVC pattern in general is what I need, but it's hard for me to get started. I'm having to learn too much all at once.
Can anybody refer me to a platform or recommend a basic set of html views & scripts that I could use as a launching pad for the MVC part?
At my company we are using ASP.Net MVC to build web applications. Such applications are meant to be hosted inside an Microsoft Internet Information Services server or in the Azure cloud.
If you start in Visual Studio 2015 with File > New ... > Project and then select Templates -> Visual C# -> ASP.Net Web Application -> MVC , Visual Studio will scaffold a project that already works in principle and where you can add your content.
See http://www.asp.net/mvc for tutorials etc.
For data persistence, Microsoft Entity Framework works well with the MVC stack, see https://msdn.microsoft.com/en-us/data/ef.aspx for more.
We currently have a very large Classic ASP website that is critical to our business. It is kept in Visual SourceSafe for version control and we have numerous developers who develop the site in Visual Studio 2005. We open the website with VS2005 directly from the Development web server. We can check the files in and out of VSS directly through VS2005 and all changes we make to the asp pages are visible on the development website immediately, without the need to check back in or copy any files.
We would like to move forward with VS2013 and TFS. Our newer websites are all in TFS and we want to standardize.
Is there a way that we can continue developing the website directly on the web server using VS2013 integrated with TFS? I have found number of articles and responses online about TFS and ASP.NET, but since we don't build classic ASP code, these don't seem to help us.
Really your development server is not where you should be doing your development, but on your local desktops, and then deploying to your development server for initial testing.
However with that said, it looks like your working directory in SourceSafe is where you have IIS pointing to on your development server. You can do the same thing with visual studio and TFS. Just have your Visual Studio workspace pointing to the same location, but checking in everything to TFS.
Edit- the bin directory for a project typically doesn't get checked in to TFS. The developer would have to make sure they build the project every time they wish to view the site on this development server to populate the bin directory.
I maintain a couple of legacy ASP.Net webforms solutions, that I have upgraded to use .Net 4.
However, they appear to be different in Visual Studio 2010, than other projects. If I open properties for one of the web projects in the solution, it looks like this:
The old-school dialog from previous versions. No fancy publishing and other neat "new" stuff.
What is going on here, and how do I fix it?
You appear to have created a New Web Site...
You're looking for Web Application it sounds like. Go to File > New > Project..., and ASP.NET Web Application is under there. You may also want ASP.NET Empty Web Application as it doesn't have some auto-generated junk in it.
I'm considering publishing an an ASP.NET MVC 3 app under a SharePoint 2010 application on IIS (not inside SharePoint as a SPSite or whatnot, just a regular IIS application for SSO-integration w. SP).
The MVC app would then only inherit some configs. It has no reference to SharePoint and SharePoint does not have any reference to it other than it being an sub application under the SharePoint 2010 app in IIS.
3-fold question:
Is it possible?
Are there any obvious issues with SharePoint 2010 running on 3.5, and my new app running on 4.0 for instance? Sufficient to use different app-pools?
I'm concerned about the inheritance of web.configs between my MVC app to SharePoint's
web.config. Are there any issues regarding web.config inheritance between these two?
UPDATE (February 27, 2013): We no longer need to use <location> XML element to stop inheritance from SharePoint to the ASP.Net MVC 3 application. We need to give FullTrust to the ASP.Net application using the <trust level="Full" originUrl="" /> XML element in the Web.Config.
Some HTTP Modules / HTTP Handlers need to be disabled from the ASP.Net MVC 3 application.
For the SharePoint 2010 scenario, I also had to move the <sectionGroup name="system.web.extensions"> XML element from the SharePoint 2010 web.config file to C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\web.config file because it conflicted with .NET 4.0. If you move it there, it will still be inherited by SharePoint web.config.
Anyway, I won't repeat all steps here.
Please see my blog post:
MVC 3 with SharePoint Server 2010:
http://samsonfr.wordpress.com/2013/02/26/recette-amliore-intgrer-une-application-asp-net-mvc-3-sous-un-site-web-iis-hbergeant-sharepoint-server-2010/
MVC 3 with WSS 3.0:
http://samsonfr.wordpress.com/2013/02/26/recette-amliore-intgrer-une-application-asp-net-mvc-sous-un-site-web-iis-hbergeant-wss-3-0-sharepoint-2007/
It's in french but I guess you can use Google translate.
Best regards,
I have tried and failed. Currently having to host the .Net 4 app on a seperate IP, which creates all kinds of cross scripting/security issues. I found some tips here: http://www.asp.net/learn/whitepapers/aspnet4/breaking-changes but couldn't get it working.
If your application will run only under Virtual folder (so it will have access to SPContext if it needs to) an not an actually under Application folder (hence not being integrated into Sharepoint at all) then I guess Asp.net MVC 3 is out of the question because of its .net 4 relation.
But. Asp.net MVC 2 is definitelly possible. I'm developing such an app and it works as expected. It took me a while to integrate it though... My integration makes it possible to only change root Sharepoint's site web.config (only add new things to it, nothing's been taken out or changed). I haven't changes even the Global.asax for routing definition.
My application is running as a virtual folder under Sharepoint Foundation 2010 Site and has access to SPContext and is also security controlled by Sharepoint (authentication is performed by the SP 2010 Site). So that's definitely possible.
But it has to be Asp.net MVC 2 since it runs on .net 3.5, the same as as Sharepoint 2010.
Visual Studio allows you to make "Web Sites" and "Web Applications", but, inside a project, can you have one within the other?
Say I have my website "www.mysite.com" and I have an application called "BudgetCalculator". One the production server, this is supposed to be located at:
www.mysite.com/BudgetCalculator
And the BudgetCalculator app contains links back to other parts of the website, like "/page1" and "/page2".
However in Visual Studio, when they're listed as two different projects, they're on the same level. When I fire up the debugger for the BudgetCalculator app, those links aren't going to point back to the main website, like they should.
Is there a way around this?
One solution would be to stop using the built-in .NET Web Server.
Use IIS, create one site, and make your Web App a Virtual Directory inside of the Web Site.
A project cannot host/contain another project in Visual Studio.
You can however create a project that sites in the directory of another higher level project when you create it, however they may not be directly linked, so you couldn't debug them both at the same time.