This is a migrated thread and some comments may be shown as answers.

Visual Studio 2008 design issue

11 Answers 114 Views

General Discussions

This is a migrated thread and some comments may be shown as answers.

Paul Robertson asked on 20 Jan 2011, 05:21 PM

Hi there

I'm trying to develop an ascx control in Visual Studio 2008 SP1. I get the 'Fail to create designer' rendering error when I switch to the VS design page. Apparently this is due to the absence of Telerik.Web.Design.dll - am I correct in asssuming this. The trouble is, I'm using the 2010.2.929.35 version of Telerik.Web.UI integrated into DotNetNuke 5.6

My questions are:
1. Is there even such Telerik.Web.Design.dll to match this bundled version of Telerik.Web.UI ?
2. Is the error just cosmetic, or does it actually result in corruption of the designer.vb file in Visual Studio?
3. Am I OK to continue my ascx DNN module despite the error, or is there a download location for the correct version of this Telerik.Web.Design.dll, as it does not appear to be included in any of the DotNetNuke installation downloads?

Thanks very much if you can clarify this for me!

Regards

11 Answers, 1 is accepted

answered on 24 Feb 2011, 10:35 PM

OK

So I have the DLL in question now, so thanks for that. Now I have it in the BIN folder of my DNN module's solution, and even added a reference to the DLL on the solution. But now, in VS2008, when I try to switch to design mode for the ascx control, instead of controls with errors, I'm actually worse off! Now the design page doesn't show up at all, and the UI just goes grey. What can be happening here? It's a bit of a farcical disaster! Is there any way of telling VS2008 to use the DLL properly!? Are the designer files corrupt, as I originally suggested? How would you go about it regenerating them from scratch?

Any help gladly received!

Regards

answered on 01 Mar 2011, 12:03 PM

Hi there

I've restarted VS many many times, but its not a software issue in that sense I don't think - its only affecting the solution that contains the new DLL, since I added the DLL to the BIN folder. So it's not to do with any of the widely discussed Office compatability issues etc. I CAN build the solution now since adding the design DLL, which is a step forward, but at the price of that it seems to have corrupted the designer file. It doesn't even make any difference if I delete the file and do the 'Convert to web application' trick - I just can't seem to generated a designer file that it can render. Has anybody else encountered this problem?

Cheers

answered on 02 Mar 2011, 10:37 PM

Hi there

It's not exactly that the designer file can't be generated, as it appears that the file is automatically created if: the file is deleted and then the 'Convert to Web Application' option is chosen for the control in question - apparently this is the best workaround. The problem is that the designer file then always crashes the edit window however you try to open it - it just goes grey and non-responsive. I've got VS2008 SP1, and there are no other versions of the DLL in the GAC - I only managed to get hold of this one by emailinfg Telerik, but as soon as I added it to my solution this problem started!

Cheers