December CTP Namespace Mapping problem

Hot Topic

One property/item to access all the properties set on the command-line
XAMLPAD integration in VISUAL Studio 2005 Beta 2?
Error on Visual Studio Tools for Office "v3" install
Reportviewer doesn't print first time I click print button
problem installing VS2005
Office addins Project Creation Failed
Sharing projects across multiple solutions
Changes to AddIn satellite DLL with new release of VS 2005.
Visual SourceSafe 2005 IDE Integration Problem with Visual Studio 2005
Undeclared Namespace error when using x:TypeArguments

Visual Studio

Accessing the domain model using code
Sparkle Interactive Designer (on Windows XP)
Problem with Add-in on client machine.
Can't get object collections to work
Do I need to Uninstall VS2005 Professional and install VS2005 Tools for the MS Office System?
How to import .ical or .ics or .vcard file into outlook programatically
VSS Internet Checkout Errors for 2 projects
PrintToPrinter failed to print
Word 2003 with VSTO 2003 stops working when .Net Framework Beta 2 is installed
Getting Started with Interactive Designer (blur with XAML & CS code)

December CTP Namespace Mapping problem

I have a scenario where I'm binding to a data object. Worked fine in the Nov release, but in the december release, It's telling me the mapping statement is missing the assembly attribuite. As such, the xaml won't complie. I tried creating a new window and trying a basic mapping statemenet as the only modification, and that fails too. Any feedback

 

my mapping statement is something like

< Mapping xmlnamespace="blah" clrnamespace="whatever" >

(ignor caps/spelling errors, i just rattled it off from memory)

Answer this question

December CTP Namespace Mapping problem

  • csgear

    To Dieter De Preester:

    another sentense is needed:

    < Mapping XmlNamespace="myList" ClrNamespace="WindowsApplication11" >

    <Window ...

      xmlns:myList="myList">

     <Window.DataContext>
        <myList:Persons>
         
        </myList:Persons>
      </Window.DataContext>

  • nikos_22

    Stephen - did you ever get round this

    I just moved to the Jan CTP from Nov CTP and am up against the exact same thing.

    It can't seem to find my Assembly references and all my "local:myThing" type statements in XAML are being rejected by the compiler.

    Thanks for any feedback you may have.



  • Nilesh Hirpara

    (BTW There is a Cider specific forum:

    http://forums.microsoft.com/MSDN/ShowForum.aspx ForumID=169&SiteID=1 where you can give feedback on Cider)

    Stephen:  there are limitations on what we support for namespace mappings in the designer in the December CTP (see http://channel9.msdn.com/wiki/default.aspx/Cider.FrequentlyAskedQuestions).

    Michael: thanks for the feedback. There are some limitations on what XAML we support (I'll detail these on the Cider Channel 9 Wiki over the holidays) however most XAML should work. Please report anything you find that doesn't work on the Cider forum.

    thanks very much

    mark

     



  • JCS

    Hello

    I have this mapping
    < Mapping XmlNamespace="myList" ClrNamespace="WindowsApplication11" >

    and in my XAML file i have

      <Window.DataContext>
        <myList:Persons>
         
        </myList:Persons>
      </Window.DataContext>


    The problem is that the compilation process fails. I get a compile error saying

    Error    1    Assembly attribute missing.    D:\Temp\WindowsApplication11\WindowsApplication11\Window1.xaml    1    68    WindowsApplication11
    Error    2    Type 'myList:Persons' could not be found. Are you missing an assembly reference     D:\Temp\WindowsApplication11\WindowsApplication11\Window1.xaml    73    6    WindowsApplication11
    Error    3    Namespace prefix 'myList' is not defined.    D:\Temp\WindowsApplication11\WindowsApplication11\Window1.xaml    73    6    WindowsApplication11
    Error    18    Unknown build error, ''myList' is an undeclared namespace. Line 73, position 6.'     D:\Temp\WindowsApplication11\WindowsApplication11\Window1.xaml    73    6    WindowsApplication11

    Kind regards
    Dieter

  • Arjang Fahim

    I just discovered, the xaml WILL compile. It runs fine, but the designer still shows the error in the task list and wont render.

  • banjaxed

    Right.  If you close the file the errors go away and the error list is what it should be.  This version of Cider appears to have a problem with many things.  It also complained about my use of {Binding Path=XXX,ElementName=YYY} complaining about "lementName" not being a property of Binding.  I guess it did not get tested with very many real XAML files, or only ones that had a certain uniformity of style.  It may also be true that they do not expect this version of Cider to be able to work with any XAML not created by Cider itself.  I guess I need to read the release notes.

  • December CTP Namespace Mapping problem
Answer this question