server.vbw & mirge.vbw

[Styre]

Hi,

I coudn't find this when i searched, so I decided to post the question.
What do the server.vbw and the mirage.vbw files do?

Thanks in advance.

Cheers, Styre

[Robin]

Looks like a dependency of the project.

Probably automatically created when your project is. Or left over from a compile.

Does it really matter?

Edit:

Visual Basic Workspace file.

[Spodi]

*.vbw files are used to keep information on the last used settings of a VB project. For example, if you open a project after deleting the *.vbw files, you won't see any open windows when you open the *.vbp file. These are not required by Visual Basic and in no way alter the end product. I recommend deleting / not including these every time you distribute your code, even if distributing the source, in case your resolution is higher than the previous user's (could cause some huge windows, which is annoying) and to speed up load time since not all code panes have to load.

[Tony]

It obviously opens the partial parts of the created project, rofl.

[Styre]

Thanks for the anwsers guys

[Tony]

I'd say it would be common sense.

[Spodi]

I'd say it would be common sense.

With an answer as vague as yours, yes, it is easy to figure out. Common sense? Maybe under the assumption everyone is programmers then yes, it is probably common knowledge.

[Robin]

Hardly common knowledge. I only had a vague understanding of it, and Styre didn't even know the actual name, just the file extension, so..

[Matt]

I didn't even know these files were there, let alone what they do. So so much for common sense. =P

[Xlithan]

I knew what they were, what they did etc. but I don't know how to stop them from saving.

[Rian]

I didn't know how to stop them from saving either (still don't). But I do know that every time I downloaded a fresh copy of 3.0.3 or MSE, I always delete them. It's a pain in the ass when every form and module pops up.

And I don't know if this has happened to any one else, but I have a clumsy habit of (and don't ask how this happens, it just does) accidentally dragging one of the work space windows up too far, and they go behind the VB tool bars and shit, and I can't get them back down. I think it was Verrigan that told to just delete the .VBW files to fix it.

[Boo]

i just exit out without saving if something goes wrong in the test compile :x.

You guys know if you open the project from it you can just do like Run -> Full Compile.

Instead of compiling the whole thing and then testing which takes forever :p

[Robin]

i just exit out without saving if something goes wrong in the test compile :x.

You guys know if you open the project from it you can just do like Run -> Full Compile.

Instead of compiling the whole thing and then testing which takes forever :p

Well, yeah.

Of course we did.

Didn't you?

[Spodi]

Or you can write the code properly, then tick some optimizations, then it'll run faster AND compile faster.

[Xlithan]

It's better to run a compiled copy. Running from the IDE doesn't always catch those little bugs. I've often found that after I've compiled the source, I find more bugs in the compiled version.

[Spodi]

It's better to run a compiled copy. Running from the IDE doesn't always catch those little bugs. I've often found that after I've compiled the source, I find more bugs in the compiled version.

Actually not really. The IDE will tell you where the line crashes, and doesn't run with any optimizations so overflows and such will still show up. I've never had the IDE run fine and the compiled not, myself. In fact, only time I ever even run compiled is if I don't plan on altering the client or server any time soon.