Edit and Continue with Linked .vb files

[teguh123]

There are 2 ways we can add .vb files.

We can add them as a link and choose not to copy. Or we can add them and copy.

The way I did it in vb.6 is equivalent with add them as link and choose not to copy.

Also what's the point of copying to target folder anyway? I want the original linked file to be updated when I change the file during debuging.

However, edit and continue doesn't work that way.

What am I missing?

[kleinma]

Unfortunatly you aren't missing anything, you just can't edit/continue on linked files in Visual Studio right now. Nor can you edit & continue when running x64 or AnyCPU configs on a 64 bit OS.

[teguh123]

That's very sad.

The current directory is set to the exact location of the .vbproj location. It's different than the output location. I guess I have to come up with way to change the current directory location to the file where I wanted it.

[teguh123]

I see. Yea. Bummer. Why I can't do that? In Vb6 I can do that just fine.

Well, what's the purpose of "copy to output directory" then?

[kleinma]

the purpose to copy to output directory is if you wanted a specific file that is NOT going to be compiled as part of your exe to be in the same directory as the compiled exe when you do build.

Imagine you added a bunch of image and text files to your project because your app was supposed to work with them when it runs. You could add these files to your project and set them to copy to the output directory. Then when you build/debug your app these files are copied to the BIN folder where your exe is generated, so it simulates when the app is installed and certain files (again that are not a compiled part of the app like exe and dll files) need to be in the exe's directory.

It really has nothing to do with linked files.