Editing and Recompiling

[TrekBiker]

Have inherited a vb project that I've opened in Visual Basic 2010 and need to edit. I'm not that familiar with it but can see the code lines that need changing.

The project communicates with an Access database, and the changes involve adding extra 'Or' options nd changing the oConnect property for a newer version of Access. Does the project have to be rebuilt after these changes? Doing so on a copy gave errors 'property OutputPath failed (not valid)' and 'can't create directory'; then warnings 'can't copy' two dlls.

 

[xwb]

Is this a VB6 or VB.net project you have inherited?

Have you tried building the project without any changes?

 

[TrekBiker]

Thanks xwb. Sorry to be vague but how would I know what sort of project it is? All I have is a copy of the original that includes bbterm.sln, which I'm opening in Visual Basic 2010 Express.

Right-click / Properties shows this file's type as Microsoft Visual Studio Solution and the hover message says version Visual Basic Express 2010.

 

[SaltyTheFrog]

Well, you do have to build it to get your changes out. Can you post the code that is failing to compile?

 

[TrekBiker]

Thanks for responses, I think I may have fixed the errors. The vb project includes references to the location of the database it communicates with. Replicating this location on my test computer has allowed the new build to go through without errors or warnings.

As an Access developer I'm still unfamiliar with vb, for example the difference between files ending in sln and vbproj, let alone the code syntax.

 

[jebenson]

.sln is a Solution, which can contain one or more projects.

.vbproj is a Project. This is where you do actual coding, etc.

https://msdn.microsoft.com/en-us/library/b142f8e7.aspx

I used to rock and roll every night and party every day. Then it was every other day. Now I'm lucky if I can find 30 minutes a week in which to get funky. - Homer Simpson

Arrrr, mateys! Ye needs ta be preparin' yerselves fer Talk Like a Pirate Day!

 

[Andrzejek]

.sln is a Solution
.vbproj is a Project
and both refer to VB.NET

VB 6.0 ('classic' VB) uses .vbp for Project (.frm for Forms, .bas for Modules, etc.)

VBA - well, all of VBA 'pieces' are either part of Word, Excel, PP, and a lot of other - not necessary Microsoft's - products.

And there is also a VB Script, to add to the confusion Microsoft made.

No wonder some people are lost...

Have fun.

---- Andy

There is a great need for a sarcasm font.