I'm currently trying to install Kendo UI from NuGet and noticed an issue. I cannot find the KendoUI.dll to reference. Is it in this package, and if not, is there a way to get around that to use it within Views?
This now possible. See the release article here, in the section Private NuGet Server and Feed.
The Kendo Nuget url is https://nuget.telerik.com/nuget you will need your Kendo account password to download it.
The files you are looking for are part of the Kendo UI server-side wrappers package. That package is (currently) not available via NuGet. According to Telerik in this answer:
We (Telerik) may create a Nuget package for Kendo UI for ASP.NET MVC
once we implement a self-hosted nuget service. This is required for
license validation because Kendo UI for ASP.NET MVC is a commercial
product. In a word this is not completely off the table but needs some
infrastructural changes. Still no clear deadline.
Related
This is all new to me. I know Dynamics CRM developing more customised forms etc, you will use the Visual Studio. Also within Visual studio you can create plugins, solutions etc.
I'm more inclined to the web resources. what I have done so far, is just to upload HTML within which has an API to call a map service LIKE google but in this case its ESRI maps as a web resource into one of the Dynamics forms. This creates my map within the specified form.
This is not however the ideal way to do this, as it will mean going to every form to load HTML.
Now ESRI has a JavaScript SDK which I would imagine, I can load into Dynamics as an external plugin to have access to ESRI javascript Library.
This is where I'm stuck at the moment.
Could anyone point me to how to install an external library into dynamics visual studio?
Also, is there a way of avoiding not having to manually add html as a web resource into every forms in Dynamics?
You can upload the 3rd party JavaScript library as a web resource of type Script (JScript).
You can create the HTML resource once and reference it on all the forms, but yes, you do need to add it to each form initially.
I've seen a lot of articles on how to change the default paths for an ASP.NET MVC project so you can relocate or rename your Controllers, Models, and Views folders by extending the RazorViewEngine and specifying new path formats.
So far, this works great but the side-effect is that it has broken the Visual Studio shortcuts for "Go to View" or "Add View...".
Any ideas on whether those shortcut options can be customized to know about the new paths I've specified?
Thanks in advance! - Scott
The Visual Studio features cannot be extended to support custom paths. However, in the ASP.NET and Web Frameworks 2012.2 update that will soon be released (you can download a preview right now from here), the Add View functionality was updated to be a lot more flexible regarding which folders will have it enabled and which won't. It now supports Add View in any folder that is anywhere under a folder called "Views".
Regarding Go To View, that was not updated because unfortunately there is no way for the VS tooling to be aware of runtime customizations made to the view engine - I agree it would be cool, though!
(BTW my source for this information is that I work on ASP.NET MVC at Microsoft.)
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've read about Single-Page Applications recently and wanted to try one out. After watching Steve Sanderson's presentation (http://channel9.msdn.com/Events/TechDays/Techdays-2012-the-Netherlands/2159) I wanted to create a Single-Page App in my Visual Studio 2010 and test it out myself. But then I found out I can't choose an SPA template anymore, as it was removed in RC version.
Now, the question is - what should I do in Visual Studio 2010 (with MVC4 installed) to be able to create an SPA? I'd like to use KnockoutJS for UI and Upshot for data, both of which I'm able to install using Nuget. I haven't found anything relevant on the Web, every single page I've been to is telling me to use the SPA template, which has been removed since.
Thanks for any suggestion!
SPA was excluded from RC because it wasn't ready in time for MVC4 release. Official ASP.NET SPA page. You can create project with MVC template and scaffold SPA via NuGet (SPA scaffolding)
For Visual Studio 2010, try using Hot Towel by John Papa.
Create an empty MVC4 app, then install a Nuget from Package Manager Console
PM> Install-Package HotTowel
Now that Visual Studio => 2010 has jQuery support, I'm wondering how I can update the project template when a new jQuery release comes out? Currently when you create a project, it automatically creates the 1.4.1 files (in VS2010), but jQuery is ever evolving, and often updates it version.
How can I tell Visual Studio to use the more recent version of jQuery (or other libraries for that matter)?
You can use NuGet
right-click on your project in Solution Explorer
click on "Manage NuGet Packages" in context menu
type "jQuery" in the search box on the top right corner of the dialog box
press Enter key and wait for results
look for "jQuery" in the results, SELECT it and click "Install" button
(after installation, you previous jquery and related files will be replaced with the latest ones)
Alternatively, you can create an Empty project and install the the nuget package(s) through the Package Manager Console. This can include ALL of the libraries that you default to.
PM> Install-Package jQuery
From there, save it as a new template, and whenever you create a new project, simply run the following terminal command before starting work.
PM> Update-Package
more info on Update-Package
You can create a new project template with jQuery 1.4.2 included: http://msdn.microsoft.com/en-us/library/ms247120%28v=VS.100%29.aspx
Automatic update have some issues. If you are using jQuery library with some additional plugin and they depend on the previous jQuery library framework then they will not work. That is why you need to think carefully before updating the jQuery library from version to version.
UPDATE:
You could modify an existing template for Visual Studio which will allow you to refer to the new version of jQuery. Here is an article about creating custom Visual Studio templates.
http://msdn.microsoft.com/en-us/library/ms247119(v=VS.80).aspx
This whole Nuget/update version model in JQuery is a huge mess! (Who designed this system?)
What I do is simply avoid the JQuery template piece in Visual Studio and place the current JQuery javascript links in ONE PLACE in your web project so its pasted into every single page......either the MVC Layout page, usercontrol, or masterpage. You can mix and match controls. But it doesnt matter as modern browsers cache these files after the first download anyway.
Now when you do a JQuery update, you can fix it in one simple place in your web project. All ECMAscripts have been done this way anyway the past 15 years using server side includes or other strategies. I'm still not sure why you want a template to stuff links in hundreds of view pages in MVC you now have to customize one by one when you get different versioned files names. I think ASP.NET MVC has gone backwards in its design for that reason.