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
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.