Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 311588

Summary:

xaml view is not rendered for attached demo projects. It works when we run the application.

Product:

z_Archived

Reporter:

Satish Nikam <satish_nikam>

Component:

ESL

Assignee:

Chuwei Huang <chuwei.huang>

Status:

NEW ---

QA Contact:

Severity:

major

Priority:

CC:

yves.yang

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Windows All

Whiteboard:

Attachments:

Description	Flags
Demp application not showing xaml view	none
demo application that does render xaml view	none

Description Satish Nikam

2010-05-04 13:21:18 EDT

xaml view is not rendered for attached project. It works when we run the application. This application shows xaml view in Visual Studio 2010. 

This application was working with previous Silverlight 3.0 builds in eclipse. It may be problem due to stripping few xaml file attributes by eclipse before sending it to browser for rendering.

Comment 1 Satish Nikam

2010-05-04 13:23:11 EDT

Created attachment 166988 [details]
Demp application not showing xaml view

Demp application not showing xaml view

Comment 2 Satish Nikam

2010-05-04 14:28:19 EDT

Created attachment 167008 [details]
demo application that does render xaml view

demo application that does render xaml view

Comment 3 Yves YANG

2010-05-04 18:57:46 EDT

The modification is only on stripping of XAML for duplicate names. It should not impact on the preview.

Comment 4 Chuwei Huang

2010-05-04 22:28:24 EDT

This is well known limitation by design.

We had created a dynamic preview solution before, which can show same effect as running. But microsoft does not like this approach. So we revert it to the static preview, which only load the current xaml in editor for preview. Therefore the preview will not work in some cases, for example,
1. The xaml file uses some external silverlight controls and assemblies which are not inside the previewer. 
2. The xaml file has some c# code for initializing the user interface. (The previewer does not load c# code.)
3. The xaml file use other xaml files. (The previewer only loads a single xaml file.)


Visual studio 2010 is so powerful, and out of the scope of our project, esl will not work in the same way as it yet.

Comment 5 Yves YANG

2010-05-05 05:15:28 EDT

Precisely, ESL uses the Silverlight's XAML resource loading to create the preview. This feature has a lot of limitations. The XAML should not have:
   1. Style,
   2. Dupliacte name
   3. Event handling
And others listed by ChuWei in comment #4. 

We do have implemented some solutions to make 1, 2 and 3 work.