[{"data":1,"prerenderedAt":297},["ShallowReactive",2],{"article-determine-sharepoint":3},{"article":4,"tags":41,"previous":56,"next":237},{"id":5,"title":6,"author":7,"body":8,"createdAt":30,"description":14,"extension":31,"img":32,"meta":33,"navigation":34,"path":35,"seo":36,"stem":37,"tags":38,"updatedAt":30,"__hash__":40},"articles\u002Farticles\u002Fdetermine-sharepoint.md","Determine SharePoint Site Master Page (in use)","[object Object]",{"type":9,"value":10,"toc":26},"minimark",[11,15,23],[12,13,14],"p",{},"Where to change the master page?",[12,16,17,18],{},"Well, if you don’t have the Publishing feature activated navigate to ",[19,20,22],"a",{"href":21},"http:\u002F\u002Fyour_server\u002Fsites\u002Fexamples\u002F_Layouts\u002FChangeSiteMasterPage.aspx","\nhttp:\u002F\u002Fyour_server\u002Fsites\u002Fexamples\u002F_Layouts\u002FChangeSiteMasterPage.aspx",[12,24,25],{},"If you do have the Publishing feature enabled you can go to Master Page on the Site Settings page, under Look and Feel category.",{"title":27,"searchDepth":28,"depth":28,"links":29},"",2,[],"2015-04-20T08:07:12.2800000-04:00","md",null,{},true,"\u002Farticles\u002Fdetermine-sharepoint",{"title":6,"description":14},"articles\u002Fdetermine-sharepoint",[39],"sharepoint","ucKyHjTyPVW98QxFFGeAY6bN3vLl8zlKK1NR1vY0_Gs",[42],{"id":43,"title":44,"body":45,"description":49,"extension":31,"img":50,"meta":51,"name":39,"navigation":34,"path":52,"seo":53,"stem":54,"__hash__":55},"tags\u002Ftags\u002Fsharepoint.md","Sharepoint",{"type":9,"value":46,"toc":47},[],{"title":27,"searchDepth":28,"depth":28,"links":48},[],"Microsoft SharePoint","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1598313183973-4effcded8d5e?ixlib=rb-1.2.1&ixid=eyJhcHBfaWQiOjEyMDd9&auto=format&fit=crop&w=675&q=80",{},"\u002Ftags\u002Fsharepoint",{"description":49},"tags\u002Fsharepoint","1yMA-SLjOHmy0x6_m2U0v9b58OVV2Jg1i0vhgXavZ7M",{"id":57,"title":58,"author":7,"body":59,"createdAt":228,"description":32,"extension":31,"img":32,"meta":229,"navigation":34,"path":230,"seo":231,"stem":232,"tags":233,"updatedAt":228,"__hash__":236},"articles\u002Farticles\u002Fupgrading-to-mvc-4-from-prior-versions.md","Upgrading to MVC 4 (from prior versions)",{"type":9,"value":60,"toc":226},[61,71,84,92,96,109,112,117,152,166,169,172,175,213,223],[12,62,63,64,67,68,70],{},"MVC 4 will happily run alongside ASP.NET MVC version 3 and .NET 4\u002FVS2010. You can thus experiment and create MVC 4 projects without fear of breaking your old applications.",[65,66],"br",{},"\n ",[65,69],{},"\n There are three main methods of upgrading to MVC 4:",[72,73,74,78,81],"ul",{},[75,76,77],"li",{},"Copy existing content into a new MVC 4 project",[75,79,80],{},"Manually upgrade the project",[75,82,83],{},"Utilize the MVC 4 NuGet package (by applying the Microsoft.AspNet.MVC package)",[12,85,86,87,67,89,91],{}," Manual Upgrade Steps:",[65,88],{},[65,90],{},"\nOpen up all the web.config files in your project and replace any lines that read as the following:",[93,94,95],"pre",{},"System.Web.Mvc, Version=3.0.0.0  \nSystem.Web.WebPages, Version=1.0.0.0  \nSystem.Web.Helpers, Version=1.0.0.0  \nSystem.Web.WebPages.Razor, Version=1.0.0.0",[12,97,98,99,67,101,103,104,106,107,67],{},"With their MVC 4 counterparts:",[65,100],{},[65,102],{},"\nSystem.Web.Mvc, Version=4.0.0.0\nSystem.Web.WebPages, Version=2.0.0.0\nSystem.Web.Helpers, Version=2.0.0.0,\nSystem.Web.WebPages.Razor, Version=2.0.0.0,",[65,105],{},"\nIn the root web.config file, add a new PreserveLoginUrl key entry:",[65,108],{},[93,110,111],{},"\u003CappSettings>  \n  \u003Cadd key=\"webpages:Version\" value=\"2.0.0.0\" \u002F>  \n  \u003Cadd key=\"PreserveLoginUrl\" value=\"true\" \u002F>  \n\u003CappSettings>",[12,113,114,115,67],{},"Now delete any references to System.Web.MVC (v3). In Solution Explorer, remove the following assembly references:",[65,116],{},[72,118,119,122,125,128,131,134,137,140,143,146,149],{},[75,120,121],{},"System.Web.Mvc (v3.0.0.0)",[75,123,124],{},"System.Web.WebPages (v1.0.0.0)",[75,126,127],{},"System.Web.Razor (v1.0.0.0)",[75,129,130],{},"System.Web.WebPages.Deployment (v1.0.0.0)",[75,132,133],{},"System.Web.WebPages.Razor (v1.0.0.0)",[75,135,136],{},"Now add references to the new versions of these assemblies:",[75,138,139],{},"System.Web.Mvc (v4.0.0.0)",[75,141,142],{},"System.Web.WebPages (v2.0.0.0)",[75,144,145],{},"System.Web.Razor (v2.0.0.0)",[75,147,148],{},"System.Web.WebPages.Deployment (v2.0.0.0)",[75,150,151],{},"System.Web.WebPages.Razor (v2.0.0.0)",[12,153,154,155,157,158,160,161,163,164,67],{},"In Solution Explorer, unload your MVC project as we are going to make some changes to the project file; this won't work if the solution is open.",[65,156],{},"\nOpen the project file  and replace any references of the ProjectTypeGuids E53F8FEA-EAE0-44A6-8774-FFD645390401 with E3E379DF-F4C6-4180-9B81-6769533ABE47.",[65,159],{},"\nSave the changes you have made and reload the project.",[65,162],{},"\nFinally, if your application or its references uses any assemblies compiled against the previous version of MVC, tell these to use MVC4 by adding binding redirect entries such as the following:",[65,165],{},[93,167,168],{},"\u003Cconfiguration>  \n  \u003Cruntime>  \n    \u003CassemblyBinding xmlns=\"urn:schemas-microsoft-com:asm.v1\">  \n      \u003CdependentAssembly>  \n        \u003CassemblyIdentity name=\"System.Web.Helpers\"  \n             publicKeyToken=\"31bf3856ad364e35\" \u002F>  \n        \u003CbindingRedirect oldVersion=\"1.0.0.0\" newVersion=\"2.0.0.0\"\u002F>  \n      \u003C\u002FdependentAssembly>  \n      \u003CdependentAssembly>  \n        \u003CassemblyIdentity name=\"System.Web.Mvc\"  \n             publicKeyToken=\"31bf3856ad364e35\" \u002F>  \n        \u003CbindingRedirect oldVersion=\"1.0.0.0-3.0.0.0\" newVersion=\"4.0.0.0\"\u002F>  \n      \u003C\u002FdependentAssembly>  \n      \u003CdependentAssembly>  \n        \u003CassemblyIdentity name=\"System.Web.WebPages\"  \n             publicKeyToken=\"31bf3856ad364e35\" \u002F>  \n        \u003CbindingRedirect oldVersion=\"1.0.0.0\" newVersion=\"2.0.0.0\"\u002F>  \n      \u003C\u002FdependentAssembly>  \n    \u003C\u002FassemblyBinding>  \n  \u003C\u002Fruntime>  \n\u003C\u002Fconfiguration>",[93,170,171],{}," ",[12,173,174],{},"Notes:",[72,176,177,180,183,186,189,192,195,198,201,204,207,210],{},[75,178,179],{},"I had to do similar updates to the web.config located in the Views directory",[75,181,182],{},"If after you build and browse to the home page, you get errors like ‘The type or namespace {fill in} does not exist in the namespace..you are missing an assembly reference’ you may need to set ‘Copy Local = True’ on a few of the references.  In particular I had to set to True for the following assemblies:",[75,184,185],{},"Microsoft.Web.Infrastructure",[75,187,188],{},"System.Web.Helpers",[75,190,191],{},"System.Web.Http",[75,193,194],{},"System.Web.Http.WebHost",[75,196,197],{},"System.Web.Mvc",[75,199,200],{},"System.Web.Razor",[75,202,203],{},"System.Web.WebPages",[75,205,206],{},"System.Web.WebPages.Deployment",[75,208,209],{},"System.Web.WebPages.Razor",[75,211,212],{},"WebGrease",[12,214,215,216,219],{},"ASP.NET MVC 4 new features - ",[19,217],{"title":218,"href":218},"http:\u002F\u002Fwww.asp.net\u002Fwhitepapers\u002Fmvc4-release-notes",[19,220,218],{"href":218,"rel":221},[222],"nofollow",[12,224,225],{},"Note: Also note .NET 4.5 is an extension to 4.0, it does not introduce a new runtime",{"title":27,"searchDepth":28,"depth":28,"links":227},[],"2015-04-20T08:07:12.3800000-04:00",{},"\u002Farticles\u002Fupgrading-to-mvc-4-from-prior-versions",{"title":58,"description":32},"articles\u002Fupgrading-to-mvc-4-from-prior-versions",[234,235],"aspnet","mvc","GE11lDkpA4HwyWPf4GsE5CSacjnBx_Va3XEsyjiSaN8",{"id":238,"title":239,"author":7,"body":240,"createdAt":287,"description":288,"extension":31,"img":289,"meta":290,"navigation":34,"path":291,"seo":292,"stem":293,"tags":294,"updatedAt":287,"__hash__":296},"articles\u002Farticles\u002Fintellisense-and-javascript-in-visual-studio-2012.md","Intellisense and JavaScript in Visual Studio 2012",{"type":9,"value":241,"toc":285},[242,245],[12,243,244],{},"In short use _references.js file with your web projects.  What is _references.js?",[12,246,247,248,252,253,67,255,257,258,67,260,262,263,67,265,267,268,67,270,272,273],{},"With the latest Visual Studio a new file _references.js is found in the scripts directory.  As you probably know, the ",[249,250,251],"code",{},"\u002F\u002F <reference path=”…” \u002F>"," syntax was introduced in Visual Studio long time ago to make you able to have intellisense in any JavaScript file to include everything defined in the JavaScript located at this path.  Said another way if you write the very first line in any JavaScript file, say “my-page.js”, and make sure the path points to the proper jQuery file, when you write code in “my-page.js”, you’ll get intellisense for everything in the jQuery file.",[65,254],{},[65,256],{},"\nThe quality of the intellisense will vary based on the referenced jQuery file, whether it’s minified file (least intellisense info, only member names, sometimes), just standard source\u002Fdebug file, or even one that VsDoc comments (best intellisense, might even have notes on what types you need to pass to methods, when defined in VsDoc comments).",[65,259],{},[65,261],{},"\nVisual Studio will give you intellisense from all files that have references in the “_references.js” file. This way you can define the global \u002F common files you use all the time. This might include some library files like jQuery, or some files you use everywhere in the project like some internal utilities files.  In addition, for related files, you can use the “\u003Creference >” syntax on top of every file to connect them (from intellisense point of view).",[65,264],{},[65,266],{},"\nThere is only one _references.js file for each project and is located in the \u002Fscripts directory.",[65,269],{},[65,271],{},"\nYou can manage this file manually or in the latest Visual Studio  release you can add\u002Fedit references via Tools > Options > Text Editor –> JavaScript –> Intellisense –> References node\n",[19,274,276],{"href":275},"\u002Fmedia\u002Farticulate-import\u002Fimage_6.png",[277,278],"img",{"style":279,"src":280,"border":281,"alt":282,"title":282,"width":283,"height":284},"background-image: none; margin: 0px; padding-left: 0px; padding-right: 0px; display: inline; padding-top: 0px; border: 0px;","\u002Farticles\u002Fimages\u002F\u002Fmedia\u002Farticulate-import\u002Fimage_thumb_6.png",0,"image",244,143,{"title":27,"searchDepth":28,"depth":28,"links":286},[],"2015-04-20T08:07:12.1900000-04:00","How to enable intellisense with Visual Studio and JavaScript","\u002Farticles\u002Fimages\u002Fimage_thumb_6.png",{},"\u002Farticles\u002Fintellisense-and-javascript-in-visual-studio-2012",{"title":239,"description":288},"articles\u002Fintellisense-and-javascript-in-visual-studio-2012",[234,295],"visualstudio","oVO-9EOZCUi_NY9jWqCmtawNfh0TKJlWULh6dhsTtJY",1781574766728]