How to make changes made to a component be updated immediately

[Ingvar Nilsen]

I have two projects in the same solution.
One of them contains a component, that is finished, and added to the
toolbox.

In the second project I have put this component on the webform.

The problem arises when I make changes to the component. These changes
are not immediately recognized in the other project. I rebuild the
whole solution, doesn't help. I finally found out that if I load
another solution and the reload the first back again, the component is
updated, but this is rather cumbersome, a more easy way would be
appreciated.

Any suggestions?

 

[John Saunders]

I have two projects in the same solution.
One of them contains a component, that is finished, and added to the
toolbox.

In the second project I have put this component on the webform.

The problem arises when I make changes to the component. These changes
are not immediately recognized in the other project. I rebuild the
whole solution, doesn't help. I finally found out that if I load
another solution and the reload the first back again, the component is
updated, but this is rather cumbersome, a more easy way would be
appreciated.

Any suggestions?

It's my understanding that this is an issue with the designers. Basically,
the designer already has an instance of the old version of the component.
Even rebuilding the solution doesn't cause the designer to release this
instance.

Have you tried doing this with all designers closed? Also, I would think
that closing the solution and reopening it would work, without opening an
intermediate solution.

John Saunders

 

[Ingvar Nilsen]

Have you tried doing this with all designers closed? Also, I would
think that closing the solution and reopening it would work, without
opening an intermediate solution.

Regardless, this is not good RAD (Rapid Application Development).
Since the VS.Net is made exactly for this, and changes to components
are made all the time during development, they should be reflected
immediately, without going through this.

Hmm. Wonder if there is a way.
Maybe setting the output path of the component's project to the bin
folder where the same component is tested would help..

 

[John Saunders]

Regardless, this is not good RAD (Rapid Application Development).

No kidding. But try it and find out if this is part of the problem. If so,
you may find a better way to get around this designer issue. But you'll
never know if you don't try.

Since the VS.Net is made exactly for this, and changes to components
are made all the time during development, they should be reflected
immediately, without going through this.

The designers and their infrastructure do not seem to have been given the
same emphasis as the rest of the Framework. Consider the scant documentation
for the design-time environment. If Microsoft were to adequately document
this area and if they were to engage with developers who want to do
more-sophisticated design-time work, then they might find and fix more of
these issues sooner.

In the absence of that, these little "minor" bugs will accumulate.

Hmm. Wonder if there is a way.
Maybe setting the output path of the component's project to the bin
folder where the same component is tested would help..

It might help at run-time, but consider that even if the runtime environment
is watching the bin folder (as ASP.NET does), that the design-time
environment might not watch the bin folder.

John Saunders