Why does the demo app(s) fail to compile? !

5 posts, 0 answers
  1. James
    James avatar
    7 posts
    Member since:
    Jan 2007

    Posted 28 Feb 2011 Link to this post

    I have downloaded the trial version of RadControls for WPF (the latest presumably as of 2011/2/27) and it fails to compile, showing massive numbers of errors. Why?

    What are these .exe files within the solution?

    I'm finding errors such as "The command "Copy .." ended with code 1." and
    "Metadata file ..ScheduleView.exe' could not be found."
    'Telerik.Windows..Examples.ScheduleView.FirstLook.ConflictCheckingDragDropBehavior.ValidateDrag( ..: return type must be .. to match overriden member ..
    etc.

    Has this demo-app been checked? Or is there something simple and obvious that I neglected to do?  Thus far nothing seems to work as prescribed.

    I'm using Visual Studio 2010 Ultimate, under Win7 x64, with 12GB of RAM.  I appreciate your time and advice,

    james hurst
    (screen-capture attached)
  2. Milan
    Admin
    Milan avatar
    1989 posts

    Posted 28 Feb 2011 Link to this post

    Hello James,

    Could you please make sure that the folder where the demos are located is not read-only and that Visual Studio is started with admin privileges. 



    Greetings,
    Milan
    the Telerik team
    Registration for Q1 2011 What’s New Webinar Week is now open. Mark your calendar for the week starting March 21st and book your seat for a walk through all the exciting stuff we ship with the new release!
  3. UI for WPF is Visual Studio 2017 Ready
  4. James
    James avatar
    7 posts
    Member since:
    Jan 2007

    Posted 28 Feb 2011 Link to this post

    I do have VS running as Administrator, and I made the folders not-readonly. Which does not appear to have made any difference.
  5. James
    James avatar
    7 posts
    Member since:
    Jan 2007

    Posted 28 Feb 2011 Link to this post

    I believe it would help to have several smaller demo apps instead of one very-large one, if these are going to require extensive troubleshooting.

    Trying to build this demo app also yields a large number of warnings, apart from failing to build. Was this rushed to release or something?  Here is a screenshot from attempting to build QuickStart_WPF..
  6. James
    James avatar
    7 posts
    Member since:
    Jan 2007

    Posted 28 Feb 2011 Link to this post

    I was trying not to get into troubleshooting until getting some feedback, but my own assumption that I wasn't screwing it up myself, was incorrect. A quick look into my problem with the demo-app revealed the cause: the post-build copy command assumes the presence of the Binaries folder outside of the Demos folder. It has to be built in-place, where the installer placed it (in Program Files(x86)) or else the entire tree copied (as, to where you normally place C# projects). So.. as Roseanne Rosanna Dana always said: "never mind"

    Note: We definitely need a set of simple demo-apps, that each show one control or small set of controls, and builds without warnings. This one is huge. When I tried to follow the help files in creating a new project, it didn't work. It would be helpful to have that siimple sample demo-app to compare against to see what I'm doing wrong. But I'll start a fresh thread for that issue.

    Thanks
Back to Top
UI for WPF is Visual Studio 2017 Ready