this.XmlLayout

11-08-2005, 8:40 PM

Hi,

After importing RPX/CS files used in .NET 1.1 into .NET 2.0 (VS2005), I noticed that the line in Initialization() changed from this.LoadLayout() into this.XmlLayout...and it embedded inline the entire contents of the RPX file as a string. 

I noticed that the .XmlLayout was generated by my double-clicking the RPX to open the code-behind. 

Prior to that, the call to LoadLayout() would not find the RPX no matter how it was referenced by my namespace and would generate runtime errors.  When the LoadLayout() call was replaced by .XmlLayout then it all worked. 

1) Is this the standard behavior from now on?  (Generation of .XmlLayout to replace .LoadLayout())

2) Does this make the RPX redundant for deployment?  Is this the reason for this--design on the RPX but deploy only the CS.

Thanks,
Jay



Re: this.XmlLayout

11-09-2005, 10:46 AM

Jay,

       Yes this is going to be the standard behavior from now on for the web projects. Reason why we did this was that it was hard to embed the resource in the web projects. Also if you see now we put the RPX file for the web projects in the app_code folder.

Also When ever you make change the RPX you need to deploy it again both the CS and the RPX. Also it gets created whenever when you add a new report to the web project.

Rakesh Jani

Re: this.XmlLayout

11-10-2005, 1:04 PM
Thank you for your response..

If that's the case, will end users still be able to modify/update the report? 

I gather it's now harder to make simple tweaks to the report by editing the RPX; this will now require the end user to have to use the End-User-Designer tool to make sure that the XmlLayout property stays in sync with the RPX...

Am I understanding this correctly?

Thanks,
Jay

Re: this.XmlLayout

11-15-2005, 12:49 PM
If the reports are not in the App_Code folder the users will still be able to update the RPX file.  But by not having the report in the App_Code folder there will not be an associated code-behind file.