locked
Cider and Interactive Designer. (Billr17) - 10/13/2006 10:18 AM PST RRS feed

  • Question

  • By: Billr17

    I read through the documentation and saw that the Cider tool will flag 
    portions of XAML code as being invalid. It seems that the code still compiles 
    and runs as aspected under Visual Studio even though Cider flags warnings. 
    However, Cider may or may not display the form depending on the warnings. How 
    safe is it to just ignore the XAML warnings produced for now? Everything 
    seems alright when compiling and running under Interactive Designer, I just 
    need something more powerful for the programming end.
    
    - Bill
    Tuesday, February 19, 2008 6:03 PM

Answers

  • By: Brennon Williams

    Howdy Bill,
    
    I hear your problems and echo them with you... It has been a bit of an issue 
    during the CTP releases over the past year with miss-matched feature support 
    sets between EID & Cider... The last few CTP's have beeen a lot closer in 
    feature support but there are some big features (merged dictionaries for 
    ResourceDictionaries) that are missing from Cider and conversley some other 
    features missing from EID.
    
    I have raised this issue several times with both the EID & Cider Dev teams, 
    and the word is that they antisipate a mirrored feature set by the time the 
    product comes to Release 1.
    
    As far as the warnings go in VS, it will really come down to the amount of 
    testing that you do on your application as to if it will run or indeed 
    compile from either product and if it does run, then the performance may 
    linger from either product as well.
    
    Unfortunately it is all about patience at the moment as well as a little 
    discovery and feedback. A lot of us are really chomping at the bit for this 
    new version...
    
    Cheers
    
     
    
    "Billr17" wrote:
    
    > I read through the documentation and saw that the Cider tool will flag 
    > portions of XAML code as being invalid. It seems that the code still compiles 
    > and runs as aspected under Visual Studio even though Cider flags warnings. 
    > However, Cider may or may not display the form depending on the warnings. How 
    > safe is it to just ignore the XAML warnings produced for now? Everything 
    > seems alright when compiling and running under Interactive Designer, I just 
    > need something more powerful for the programming end.
    > 
    > - Bill
    Tuesday, February 19, 2008 9:56 PM
  • By: Unni Ravindranathan (MS)

    Theoretically, Expression Interactive Designer should not product markup
    that is invalid. Also, Cider should be able to consume any markup that
    Expression Interactive Designer produces (and vice versa). It is likely that
    there are bugs that may prevent this workflow. Please be assured that they
    will def. be fixed (if you take the time to report them, they better be
    fixed :)).

    Thanks,
    -Unni

    "Billr17" <Billr17@discussions.microsoft.com> wrote in message
    news:31001B6E-269F-410D-89CB-4C0615CE0990@microsoft.com...
    >I read through the documentation and saw that the Cider tool will flag
    > portions of XAML code as being invalid. It seems that the code still
    > compiles
    > and runs as aspected under Visual Studio even though Cider flags warnings.
    > However, Cider may or may not display the form depending on the warnings.
    > How
    > safe is it to just ignore the XAML warnings produced for now? Everything
    > seems alright when compiling and running under Interactive Designer, I
    > just
    > need something more powerful for the programming end.
    >
    > - Bill
    Tuesday, February 19, 2008 9:57 PM

All replies

  • By: Brennon Williams

    Howdy Bill,
    
    I hear your problems and echo them with you... It has been a bit of an issue 
    during the CTP releases over the past year with miss-matched feature support 
    sets between EID & Cider... The last few CTP's have beeen a lot closer in 
    feature support but there are some big features (merged dictionaries for 
    ResourceDictionaries) that are missing from Cider and conversley some other 
    features missing from EID.
    
    I have raised this issue several times with both the EID & Cider Dev teams, 
    and the word is that they antisipate a mirrored feature set by the time the 
    product comes to Release 1.
    
    As far as the warnings go in VS, it will really come down to the amount of 
    testing that you do on your application as to if it will run or indeed 
    compile from either product and if it does run, then the performance may 
    linger from either product as well.
    
    Unfortunately it is all about patience at the moment as well as a little 
    discovery and feedback. A lot of us are really chomping at the bit for this 
    new version...
    
    Cheers
    
     
    
    "Billr17" wrote:
    
    > I read through the documentation and saw that the Cider tool will flag 
    > portions of XAML code as being invalid. It seems that the code still compiles 
    > and runs as aspected under Visual Studio even though Cider flags warnings. 
    > However, Cider may or may not display the form depending on the warnings. How 
    > safe is it to just ignore the XAML warnings produced for now? Everything 
    > seems alright when compiling and running under Interactive Designer, I just 
    > need something more powerful for the programming end.
    > 
    > - Bill
    Tuesday, February 19, 2008 9:56 PM
  • By: Unni Ravindranathan (MS)

    Theoretically, Expression Interactive Designer should not product markup
    that is invalid. Also, Cider should be able to consume any markup that
    Expression Interactive Designer produces (and vice versa). It is likely that
    there are bugs that may prevent this workflow. Please be assured that they
    will def. be fixed (if you take the time to report them, they better be
    fixed :)).

    Thanks,
    -Unni

    "Billr17" <Billr17@discussions.microsoft.com> wrote in message
    news:31001B6E-269F-410D-89CB-4C0615CE0990@microsoft.com...
    >I read through the documentation and saw that the Cider tool will flag
    > portions of XAML code as being invalid. It seems that the code still
    > compiles
    > and runs as aspected under Visual Studio even though Cider flags warnings.
    > However, Cider may or may not display the form depending on the warnings.
    > How
    > safe is it to just ignore the XAML warnings produced for now? Everything
    > seems alright when compiling and running under Interactive Designer, I
    > just
    > need something more powerful for the programming end.
    >
    > - Bill
    Tuesday, February 19, 2008 9:57 PM
  • By: Billr17

    Thank you for the responses guys.
    
    "Billr17" wrote:
    
    > I read through the documentation and saw that the Cider tool will flag 
    > portions of XAML code as being invalid. It seems that the code still compiles 
    > and runs as aspected under Visual Studio even though Cider flags warnings. 
    > However, Cider may or may not display the form depending on the warnings. How 
    > safe is it to just ignore the XAML warnings produced for now? Everything 
    > seems alright when compiling and running under Interactive Designer, I just 
    > need something more powerful for the programming end.
    > 
    > - Bill
    Tuesday, February 19, 2008 9:57 PM