This bit of code in app.xaml.cs causes the error: 

private void Application_Startup(object sender, StartupEventArgs e)

{ // Load the main control

this.RootVisual = new Page(); }

Which is strange because I think that is part of the template - so maybe I have set things up incorrectly. I have using System.Windows.Browser; I thought it was because there was no reference to System.Web at first, but that can't be used in a Silverlight app I discovered.

Any help appreciated.

Thanks

If it's a runtime exception, I think it's a xml namespace declaration in a xaml file that raise the exception. Maybe you forgot to add the assembly part.
Ex:

<UserControl xmlns="http://schemas.microsoft.com/client/2007"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    xmlns:ucaya="clr-namespace:Ucaya.Silverlight.Controls;assembly=Ucaya.Silverlight"   

Thierry Bouquain
Ucaya
http://www.ucaya.com

Thanks for your reply. 

It's a compile-time error.

I don't think there is an assembly reference. Do you always need one? This is my first time looking at silverlight and this is just copied and pasted code from an example.

The code is looking for a UserControl names Page. Do you have a Page.xaml and/or Page.xaml.cs in your project?  It should have been created for you when you ran the Silverlight Application wizard.

The two files are there yes.

Hi:

peterdungan:

Thanks for your reply. 

It's a compile-time error.

I don't think there is an assembly reference. Do you always need one? This is my first time looking at silverlight and this is just copied and pasted code from an example.

  Could you tell us how do you create new Silverlight projects? If you're using wizard to do so you don't have to copy and paste any code.

Regards

Sincerely,
Allen Chen
Microsoft Online Community Support

Please remember to mark the replies as answers if they help and unmark them if they provide no help.

I just select new project and then silverlight in VS 2008.

I'm getting this same error on another small project on the same machine. Got a couple of other things working fine in the meantime.

Fixed now. It's happening when the namespace is specified incorrectly I think. Thanks for the replies