I got kendo.mvc dll from telerik team, can we get reference of this dll through Nuget?
Is there something that I am missing?
Have you read the Telerik documentation? They also offer full Visual Studio integration (setup guide here).
I am struggling to find out whats wrong with MVC 5 (Visual Studio 2015) Ninject dependency injection. In MVC 4 (Visual Studio 2013), it was quite straight forward to add Ninject with Nuget Package Manager(UI) but don't seems like the case with MVC 5 (VS 2015).
After some unsuccessful attempts, I rather used Package Manager Console and got Nuget and Nuget.Web.Common both packages installed.To my surprise, I can't find my NinjectWebCommon.cs file in App_Start folder now.
I am wondering if MVC 5 has changed the concept of dependency injection or I am doing something wrong here?
You need to install the Ninject.MVC5 package. This will add (amongst other things) the NinjectWebCommon.cs file in App_Start.
I want to code a VSPackage and need to get the selected items from Source Control Explorer History. I'm pretty sure that I need VersionControlExt, but I can't find the namespace Microsoft.VisualStudio.TeamFoundation.VersionControl using Visual Studio 2013. Can you help me?
You can use a NuGet package Microsoft.TeamFoundationServer.ExtendedClient. I'm not sure if these are too new to work against VS2013 but it's easiest to test.
If the NuGet package doesn't work, you can get the DLLs on your machine. These DLLs are stored in the Private Assembly cache of Visual Studio. You can edit the register to allow Visual Studio to search through these folders. See the first step of this post for details: Step 1: Help Visual Studio Find Team Foundation Assemblies
I know I can download the "April CTP" to get F# 2.0 for .NET 2.0. But I need FSC and F# Interactive for .NET 4.0. On a machine with VS 2010 installed, it ends up in C:\Program Files (x86)\Microsoft F#\v4.0. Is there a redistributable for this?
If you installed Visual Studio 11 Beta or Visual Studio 2012, I recommend you check the following path, where you will find Fsi.exe and Fsc.exe.
C:\Program Files (x86)\Microsoft SDKs\F#\3.0\Framework\v4.0
Others have provided good answers; I'll summarize and add one more bit (2nd bullet):
We don't have any polished story here yet. We're working on one.
In the case of the compiler, you may be able to get by with the fsc.exe in the April CTP (it is capable of referencing .NET 4.0 assemblies and building .NET 4.0 assemblies, even though the compiler itself runs on 2.0). (Note that for building project files, you might also need the right Microsoft.FSharp.targets imported; I haven't worked all that through...)
If you were to copy the right assemblies and targets files from a VS2010 install to another machine, that would work, but offhand I don't know if that violates the VS license.
The existing downloadable "redist" does only contain FSharp.Core.dll.
(possibly see also this for a similar discussion but no extra info, as well as this Connect request)
The redistributable, for the F# runtime, is available at the following link, but unfortunately doesn't include the compiler or F# interactive:
http://www.microsoft.com/downloads/details.aspx?FamilyID=5f0a79f8-925f-4297-9ae2-86e2fdcff33c&displaylang=en
If you already have VS2010 installed on the machine there shouldn't be no need to install it, as the compiler, fsi, and F# runtime will be installed with VS. It should be just a matter of adding the directory containing the compiler to the path, so the shell can find it (if you want to use the compiler/fsc from the command-line).
This is an old question, but I came across it and thought that I'd add an update for people who find it through Google:
The current version of the F# CTP (April 2011) includes both .NET 2.0 and .NET 4.0 binaries, including FSI.exe. On my install...
.NET 2 = C:\Program Files (x86)\FSharp-2.0.0.0\bin\
.NET 4 = C:\Program Files (x86)\FSharp-2.0.0.0\v4.0\bin\
I think that there is no standalone installation of F# for .NET 4.0 (similar to the standalone installation for .NET 2.0). The reason probably is that F# for .NET 4.0 is simply meant to be distributed only as part of Visual Studio 2010 and not separately (just like other core Visual Studio languages).
If you need to use fsi.exe and fsc.exe for .NET 4.0 on a machine that doesn't have Visual Studio installed, you'll probably need to copy them together with the referenced libraries. This shouldn't be that difficult - you only need assemblies from "C:\Program Files (x86)\Microsoft F#\v4.0" together with FSharp.Core.dll (which should be added to the GAC) and (I think) also ISymWrapper.dll (but I'm not quite sure where this is located).
I am using WSPBuilder on Visual Studio 2010 to create a feature with a feature receiver assembly for SharePoint 2010. When I try to build the WSP using WSP Builder I get this message in the output window:
The assembly MyAssembly.dll is unmanaged. The assembly will be excluded from the WSP package!
The defined Project Assembly seems not to be a valid assembly!
Solution compatibility: SharePoint 2010
The resulting WSP that gets built does not contain my DLL.
My DLL is strongly named, and I cant think of any other obvious reasons why this is happening.
Any idea why WSPBuilder is not able to package my assembly in the WSP?
Ahh... Found the answer. My code was getting compiled against .Net Framework 4.0. Changed it to .Net Framework 3.5 and Voila! WSP gets built without any problems...