Move dependencies to NuGet packages about cookietempdata HOT 8 CLOSED

Yea, this might be an error due to some of Msft's recent MVC changes. I'd have to look, but don't have a lot of time. If you can diagnose, it'd be helpful

from cookietempdata.

The project is on MVC 3 and I've tested it with MVC 5.2.X.

Maybe something like <dependency id="Microsoft ASP.NET MVC" version="[3,6)" /> for a start.

from cookietempdata.

@jkodroff: any chance you can take a look into this? I'd like to resolve #11 but it'd be nice to have the dependencies as Nuget packages already.

from cookietempdata.

I believe (but am by no means certain) that MVC 3 could no longer be supported because MVC 3 is not delivered as a NuGet package - it's installed to the system.

Again, not sure, but I believe we could do [4,6), and I'd certainly be willing to try it.

The question is whether @brockallen is willing to cease support for MVC 3 if necessary, per my question above.

from cookietempdata.

Well, since we have a working solution for MVC3, if people want it they can get the old code/ NuGet. So yea, I'm fine w/ moving to MVC4 or 5.

from cookietempdata.

Any PR forthcoming?

from cookietempdata.

Yes. This week. I promise. Sorry for the delay.

from cookietempdata.

I'd not knock yourself out -- ASP.NET 5 is right around the corner so this might be a bit late to bother with.

from cookietempdata.