.NET Client deployment!

  • Thread starter Thread starter Atmapuri
  • Start date Start date
A

Atmapuri

Hi!

I am looking at how to make use of the client
framework, but found the following problems:

The client framework does not include System.Designer
assembly. Without this assembly it is not possible to
register the components to be displayed on the toolbox.
(contains ToolboxItem attribute).

Is it somehow possible to produce two assemblies, where
one will register the components from the first to be
displayed on the toolbox within VS.IDE, but the actual
application will not require it's deployment?

I checked C# partial classes, but they require, that all
the definitions are within the same assembly which
defeats the purpose here.

Thanks!
Atmapuri
 
Unclear.

Just use the full framework on your dev machine. You have a project option
to limit your project to the client profile...

For now it seems to me you are trying to use the client profile on a
development machine which is likely not the typical use case...
 
Hi!
Unclear.

Just use the full framework on your dev machine. You have a project option
to limit your project to the client profile...

For now it seems to me you are trying to use the client profile on a
development machine which is likely not the typical use case...
Click to expand...

Some components I use in my project are within my own
assemblies. In order to have those components from my own
assemblies available on the Toolbox, these assemblies have to
a reference System.Designer assembly which contains the
definition of the ToolboxItem attribute.

When trying to use the client framework, this becomes to be
a problem, because System.Designer is not part of the client
framework.

Clearly, VS.NET has to have some way to get components
displayed on the toolbox and yet not use the ToolboxItem
attribute directly from the same assemblies which will
be deployed.

Thanks!
Atmapuri
 
Some components I use in my project are within my own
assemblies. In order to have those components from my own
assemblies available on the Toolbox, these assemblies have to
a reference System.Designer assembly which contains the
definition of the ToolboxItem attribute.

When trying to use the client framework, this becomes to be
a problem, because System.Designer is not part of the client
framework.

Clearly, VS.NET has to have some way to get components
displayed on the toolbox and yet not use the ToolboxItem
attribute directly from the same assemblies which will
be deployed.
Click to expand...

Sorry, I better understand now.

This is certainly possible as MS controls are both deployed with the client
profile and yet provide a design time experience. So it seems they don't
have this dependency (Reflector or referencesource.microsoft.com should
allow to see how they are done (i.e. they lack this attribute) but perhaps
not how they are registered). I recently saw also that it seems VS uses
particular convention for design time assemblies (for example to support
sharing Silverlight, WPF design time support).

I found several method such as
http://www.codeproject.com/KB/macros/addcontrol2toolbox.aspx to
programmatically register controls in the VS toolbox. Also according to the
documentation it seems this attribute will be available in the .NET 4 Client
Profile. Moreover, my understanding is that 3.5 client profile can be
installed only if you have no framework installed
(http://msdn.microsoft.com/en-us/lib...framework_client_profile_deployment_scenarios)
when version 4 will be installable even if a previous version is installed.

So if you are just starting an application that targets the client profile,
targetting 4.0 rather than 3.5 could be perhaps much more usefull....

Sorry for the poor help.
 
Back
Top