Problem with Databinding example

[Brian]

I have been trying to extract the Databinding example and build from there an example that will do what I am needing to do. I have just not been able to get it to run.

Does someone have the example by itself, not included in the big example_C#?

Thanks,

[Yavor]

Hello Brian,

I have extracted the Map DataBinding example for you in a separate Silverlight application. Just put in your Bing maps key and you are ready to go.

We always appreciate your feedback and in order to improve our examples can you please share what are the problems that you experienced when you tried extracting this example?

Regards,
Yavor Ivanov
the Telerik team

[Brian]

Yavor, thank you for sending that sample. The sample runs fine, with the exception of the Map. No map is displayed. I put my Bing Key in, compile and run. No map display. I do see the POI's etc, just not the map.

With regard to the project examples that are included with the demos. I run the main Examples_CS and compile it. I get the following compile errors which I am still picking thru;

-------------

Warning 1 Client proxy generation for service 'ExamplesWeb.NorthwindDataService' failed: Generating metadata files...
Warning: Unable to load a service with configName 'ExamplesWeb.NorthwindDataService'. To export a service provide both the assembly containing the service type and an executable with configuration for this service.

Details:Either none of the assemblies passed were executables with configuration files or none of the configuration files contained services with the config name 'ExamplesWeb.NorthwindDataService'.

Warning: No metadata files were generated. No service contracts were exported.
 To export a service, use the /serviceName option. To export data contracts, specify the /dataContractOnly option. This can sometimes occur in certain security contexts, such as when the assembly is loaded over a UNC network file share. If this is the case, try copying the assembly into a trusted environment and running it.

GridView.Silverlight

Warning 2 Client proxy generation for service 'ExamplesWeb.NorthwindDataService' failed: Generating metadata files...
Warning: Unable to load a service with configName 'ExamplesWeb.NorthwindDataService'. To export a service provide both the assembly containing the service type and an executable with configuration for this service.
    Details:Either none of the assemblies passed were executables with configuration files or none of the configuration files contained services with the config name 'ExamplesWeb.NorthwindDataService'.

Warning: No metadata files were generated. No service contracts were exported.
 To export a service, use the /serviceName option. To export data contracts, specify the /dataContractOnly option. This can sometimes occur in certain security contexts, such as when the assembly is loaded over a UNC network file share. If this is the case, try copying the assembly into a trusted environment and running it.

 TreeView.Silverlight

Warning 3 Client proxy generation for service 'ExamplesWeb.NorthwindDataService' failed: Generating metadata files...
Warning: Unable to load a service with configName 'ExamplesWeb.NorthwindDataService'. To export a service provide both the assembly containing the service type and an executable with configuration for this service.
    Details:Either none of the assemblies passed were executables with configuration files or none of the configuration files contained services with the config name 'ExamplesWeb.NorthwindDataService'.

Warning: No metadata files were generated. No service contracts were exported.
 To export a service, use the /serviceName option. To export data contracts, specify the /dataContractOnly option. This can sometimes occur in certain security contexts, such as when the assembly is loaded over a UNC network file share. If this is the case, try copying the assembly into a trusted environment and running it.

 DataFilter.Silverlight

Warning 4 Client proxy generation for service 'ExamplesWeb.NorthwindDataService' failed: Generating metadata files...
Warning: Unable to load a service with configName 'ExamplesWeb.NorthwindDataService'. To export a service provide both the assembly containing the service type and an executable with configuration for this service.
    Details:Either none of the assemblies passed were executables with configuration files or none of the configuration files contained services with the config name 'ExamplesWeb.NorthwindDataService'.

Warning: No metadata files were generated. No service contracts were exported.
 To export a service, use the /serviceName option. To export data contracts, specify the /dataContractOnly option. This can sometimes occur in certain security contexts, such as when the assembly is loaded over a UNC network file share. If this is the case, try copying the assembly into a trusted environment and running it.

 DataVirtualization.Silverlight

Warning 5 Client proxy generation for service 'ExamplesWeb.NorthwindDataService' failed: Generating metadata files...
Warning: Unable to load a service with configName 'ExamplesWeb.NorthwindDataService'. To export a service provide both the assembly containing the service type and an executable with configuration for this service.
    Details:Either none of the assemblies passed were executables with configuration files or none of the configuration files contained services with the config name 'ExamplesWeb.NorthwindDataService'.

Warning: No metadata files were generated. No service contracts were exported.
 To export a service, use the /serviceName option. To export data contracts, specify the /dataContractOnly option. This can sometimes occur in certain security contexts, such as when the assembly is loaded over a UNC network file share. If this is the case, try copying the assembly into a trusted environment and running it.

 DomainDataSource.Silverlight

Warning 6 Client proxy generation for service 'ExamplesWeb.NorthwindDataService' failed: Generating metadata files...
Warning: Unable to load a service with configName 'ExamplesWeb.NorthwindDataService'. To export a service provide both the assembly containing the service type and an executable with configuration for this service.
    Details:Either none of the assemblies passed were executables with configuration files or none of the configuration files contained services with the config name 'ExamplesWeb.NorthwindDataService'.

Warning: No metadata files were generated. No service contracts were exported.
 To export a service, use the /serviceName option. To export data contracts, specify the /dataContractOnly option. This can sometimes occur in certain security contexts, such as when the assembly is loaded over a UNC network file share. If this is the case, try copying the assembly into a trusted environment and running it.

 DataForm.Silverlight

Error 7 Unexpected error creating debug information file 'C:\Program Files (x86)\Telerik\RadControls for Silverlight Q1 2011 SP1\Demos\Examples\Calendar\obj\Debug\Calendar.PDB' -- 'Unspecified error ' Calendar.Silverlight

Warning 8 A custom tool 'ResXFileCodeGenerator' is associated with file 'Localization\French.resx', but the output of the custom tool was not found in the project.  You may try re-running the custom tool by right-clicking on the file in the Solution Explorer and choosing Run Custom Tool. 

----------------

I have fixed what I can find so far.  

I think that a better way to present the demo applications is individual projects vice one huge solution with tons of projects under it. I may be the only one but when I am looking for a sample of what I need to do, I would rather have the single solitary project to dive into. It reduces the confusion factor for those of us new to the Silverlight game.

Admittedly this is my first Silverlight project, and naturally it is a whopper of a project. Luckily I have lots of time for it, so I appreciate all that you guys have taught and done for me.

Brian

[Brian]

I found the problem with why it would show a grey screen and the points.

Needed to set .Web project as the StartUp Project, and the .aspx page as startup page explicitly and from then on it worked.