Cannot use "Edit and continue" in Visual Studio 2005

Hi,

I'm writing a plugin for an external program (MapWindow) using VB.NET and Visual Studio 2005. The project builds as a class library (.dll). The debugger starts the external program that loads the project. This works fine but in break mode I cannot edit the source files, they are locked for editing.

Does anybody have an idea why the Edit and continue feature is not available in this scenario? I've checked all the obvious settings and other projects can be edited while debugging.
Note that the output path for the build is not the default debug folder, the project has to build in the plugin folder of the external program. Could this be the problem?

TIA
JosPAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

strickddCommented:
There are only certain project types that allow for the editing while running the program. These are any application types that can be compiled on the fly (i.e. websites). If they cannot compile on the fly, you cannot make changes while in debug.
0
JosPAuthor Commented:
Not sure what you mean with compile on the fly.
This project type is basically the same as for example an add-in for any of the Office products. I never had any trouble using edit and continue with those projects.
0
strickddCommented:
when I say "compile on the fly" I mean that it is NOT REQUIRED that you build the project to use it. For example, if you create a website and just run it, IIS will automatically compile the website for you. While in debug, if you make a change IIS will detect this and recompile the site "on the fly".

If you are working with a project that requires the compiler to create the DLL, then you will need to stop debugging and re-run/re-compile the application to make the changes.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JosPAuthor Commented:
Still don't understand why it doesn't work in this scenario, but I accept that it just doesn't, for some reason...
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.