Compatible with MVC Preview Release 3?

Last post 07-13-2008 7:55 PM by xxxd. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • 07-04-2008 1:25 PM

    • ylDave
    • Top 500 Contributor
    • Joined on 05-22-2008
    • Wannabe Slacker
    • Points 21

    Compatible with MVC Preview Release 3?

    Is the code compatible with the latest preview release? I downloaded and compiled the project in the Web folder and am getting compile errors; don't know where these types should reside:

    Error 1 The type or namespace name 'ActionFilterAttribute' could not be found (are you missing a using directive or an assembly reference?) Web\Filters\CacheFilter.cs 7 41 Web
    Error 2 The type or namespace name 'ActionFilterAttribute' could not be found (are you missing a using directive or an assembly reference?) WebSites\kigg\Web\Filters\CompressFilter.cs 8 35 Web
    Error 3 The type or namespace name 'FilterExecutedContext' could not be found (are you missing a using directive or an assembly reference?) Web\Filters\CacheFilter.cs 24 47 Web
    Error 4 'RouteCollection' is an ambiguous reference between 'System.Web.Routing.RouteCollection' and 'System.Web.Mvc.RouteCollection'  WebSites\kigg\Web\Global.asax.cs 18 43 Web
    Error 5 The type or namespace name 'FilterExecutingContext' could not be found (are you missing a using directive or an assembly reference?) Web\Filters\CompressFilter.cs 10 48 Web
    Error 6 'Kigg.CompressFilter' is not an attribute class (7-10 dups)

    Error 10 The type or namespace name 'NonAction' could not be found (are you missing a using directive or an assembly reference?) WebSites\kigg\Web\Controllers\StoryController.cs 68 10 Web
    Error 11 The type or namespace name 'NonActionAttribute' could not be found (are you missing a using directive or an assembly reference?) Web\Controllers\StoryController.cs 68 10 Web
    Error 12 'Kigg.CompressFilter' is not an attribute class Web\Controllers\StoryController.cs 82 10 Web
    Error 13 'Kigg.CacheFilterAttribute' is not an attribute class Web\Controllers\StoryController.cs 83 10 Web
    Error 14 'Kigg.CompressFilter' is not an attribute class Web\Controllers\StoryController.cs 120 10 Web
    Error 15 'Kigg.CompressFilter' is not an attribute class Web\Controllers\StoryController.cs 141 10 Web
    Error 16 'Kigg.CompressFilter' is not an attribute class Web\Controllers\StoryController.cs 176 10 Web
    Error 17 'Kigg.CompressFilter' is not an attribute class Web\Controllers\StoryController.cs 211 10 Web
    Error 18 'Kigg.CompressFilter' is not an attribute class Web\Controllers\StoryController.cs 239 10 Web
    Error 19 'Kigg.CompressFilter' is not an attribute class WebSites\kigg\Web\Controllers\StoryController.cs 261 10 Web
    Error 20 'Kigg.CompressFilter' is not an attribute class Web\Controllers\StoryController.cs 310 10 Web
    Error 21 'Kigg.CompressFilter' is not an attribute class Web\Controllers\StoryController.cs 344 10 Web
    Warning 22 The custom tool 'MSLinqToSQLGenerator' failed while processing the file 'Models\Kigg.dbml'. 

    Here's diff for my Web.csproj file:

    Old:

        <Reference Include="System.Web.Mvc, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
          <SpecificVersion>False</SpecificVersion>
          <HintPath>..\..\..\..\..\..\Program Files\Microsoft ASP.NET MVC Preview 2\Assemblies\System.Web.Mvc.dll</HintPath>

    New:

        <Reference Include="System.Web.Extensions, Version=3.6.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
          <RequiredTargetFramework>3.5</RequiredTargetFramework>
     

    Filed under:
  •  Advertisement

    Featured Advertisement

     
  • 07-06-2008 11:15 AM In reply to

    • xxxd
    • Top 10 Contributor
    • Joined on 12-18-2006
    • Slacker
    • Points 17,720

    Re: Compatible with MVC Preview Release 3?

    According to the kigg documention (scattered in the tutorial article and blogs), the latest version is compatible with MVC preview 2, in which ActionFilterAttribute is one of the features. I have not read anywhere that Kigg has upgraded to MVC 3.

    I am no expert in any of the MVCs or Kigg, however, the quick succession of upgrades is problematic sometimes. For example, the newest control tool kit uses 3.5, however, to be able to add the controls to the toolbox, you still have to install system.web.extension.1.06..., because most of the extenders (autocomplete textbox..) still uses extention 1.0x.

    Just my opinion. Hope it helps

  • 07-08-2008 10:52 AM In reply to

    • ylDave
    • Top 500 Contributor
    • Joined on 05-22-2008
    • Wannabe Slacker
    • Points 21

    Re: Compatible with MVC Preview Release 3?

    xxXd:

    According to the kigg documention (scattered in the tutorial article and blogs), the latest version is compatible with MVC preview 2, in which ActionFilterAttribute is one of the features. I have not read anywhere that Kigg has upgraded to MVC 3.

     

    Thanks Xun!  I hadn't read that either but had hoped 3 would be backward compatible with 2 but apparently not.

    The msdn links to download preview 2 are no longer working so I found the source for MVC Preview 2 on CodePlex, compiled it and replaced my references with the new assemblies and it is working now.

    Dave

     

     

     

  • 07-13-2008 3:02 PM In reply to

    • ylDave
    • Top 500 Contributor
    • Joined on 05-22-2008
    • Wannabe Slacker
    • Points 21

    "Strong name signature could not be verified" on routing assembly at deployment

    The setup I described worked fine locally but I got an error on the Routing assembly when I deployed to my server.

    I found a post on ScottGu's blog about a MVC Preview Refresh with a link to Codeplex and copied out the Routing and Abstractions assemblies to my server and that got me past the naming issue on the assemblied.

    Dave 

  • 07-13-2008 7:55 PM In reply to

    • xxxd
    • Top 10 Contributor
    • Joined on 12-18-2006
    • Slacker
    • Points 17,720

    Re: "Strong name signature could not be verified" on routing assembly at deployment

    Glad that you got everything working and Thanks for sharing.

Page 1 of 1 (5 items)