We have a ASP.Net site used webForms. MasterPage, menus, aspx pages etc.
is there a way to integrate blazor components directly into aspx pages?
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.
I'm using SharePoint 2010 and I have developed webparts at visual studio 2010. I'm already using WSP to deploy my web application into server, but still should create and add the webpart manually through SharePoint site. Is there any way that we can deploy the application and automatically create and add all webparts into the site?
Generally web parts are added to pages using features. Basically you create one site collection feature to deploy web part files to web part gallery and web scope feature which adds this web parts to pages (for example default site page).
I am wondering if there is a "basic" asp.net web api template. I only see one "web api" project and it brings out of bit of stuff in and not sure if all of it I need.
You can either:
1) Create a new MVC4 project > choose Web API template - but that, as you point out, brings in a lot of stuff, including Modernizer, jQuery, Knockout and so on
2) Create a new ASP.NET empty Web application and install Web API web host from Nuget:
PM> Install-Package Microsoft.AspNet.WebApi
You then end up with a very clean, basic project, including only the necessary DLLs.
3) If you want to self host Web API (not do an ASP.NET MVC4 project), you can create a new console application and install Web API self host from Nuget:
PM> Install-Package Microsoft.AspNet.WebApi.SelfHost
which is perfect for lightweight services, but obviously you don't host inside IIS anymore so there are additional release/deployment considerations. You can read more about self host here -> http://www.asp.net/web-api/overview/hosting-aspnet-web-api/self-host-a-web-api
For Mvc 5 in VS 2015, I select empty project template and check WebApi section. It give me clean project with just WebApi references installed.
My suggestion goes for Empty ASP.NET Web API Project Template, which is a VS extension.
There is a pretty good demonstration of it in this Code Project article.
I use it without any sort of problems and it really is lighter than default WebAPI template.
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.
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.