Moving from .Net 2 -> 3.5 SP1 WindowsForms: WindowsForms ControlDesigner / CollectionEditor missing ?

Question

I'm preparing to move some project from .Net 2.0 to 3.5SP1. I've noticed, that for some UI Controls the ControlDesigner / CollectionEditor Class seems to be missing in 3.5 ( ClientProfile ). What is the best practice to convert / replace these depencies or must I consider a complete rewrite of these components ? The error occured when switching the projects target framework from 2.0 to 3.5 without changing anything on the sourcecode.

Answer 1

Ok, I did a repair install of .net 3.5 sp1 which solved the problem. Nevertheless one question is left open:

I have an assembly with controls which include designer support. If I want to deploy the client profile only, I would have to make a separate assembly with the designer support only of certain controls, to be able to ship the application using these controls without having the need to deploy the full .Net package. ? Or if the designers are not used at runtime by the application, can I deploy the client profile ?

Answer 2

Are the UI Controls self written, third-party-controls or the basic controls delivered with .NET itself?

If you just use the controls delivered with .NET it should work or sth. went wrong with the installation of the visual studio? Which VS-Version do you use?

Answer 3

Designers should be missing in the ClientProfile. Do you think clients ever need the designers? Just use the complete 3.5 installation for development.