VB.net Project Structure
Good Day Experts
I am looking for reference material help. My most recent programming experience was with vb.net. I essentially taught myself with books and online tutorials.
The last company I worked was small with 3 people in IT and I was one of them. With the company being small, my projects were mainly small one off applications.
I am looking for guidelines on how to structure a vb.net project in VS that uses best practices and is scalable. Is there anything out there that can help with naming conventions, where to put global variables and connection information etc.
If I constructed my question without enough information please ask questions and I will do my best in providing more details.
Thanks,
jimbo99999
I am looking for reference material help. My most recent programming experience was with vb.net. I essentially taught myself with books and online tutorials.
The last company I worked was small with 3 people in IT and I was one of them. With the company being small, my projects were mainly small one off applications.
I am looking for guidelines on how to structure a vb.net project in VS that uses best practices and is scalable. Is there anything out there that can help with naming conventions, where to put global variables and connection information etc.
If I constructed my question without enough information please ask questions and I will do my best in providing more details.
Thanks,
jimbo99999
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I am trying to resurrect my VB.net career and your replies and reference materials look like a good start.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you for your suggested readings and references. I appreciate the help.
First, there are no fixed rules... just guidelines which over the period of years, you will end up customizing according to your comfort level.
First, check out this index,
https://docs.microsoft.com
if you already have, then
https://docs.microsoft.com
Global variables - depending upon your needs, can be in a class or can be Constants - accessible for the entire project, could be Enums as well.
As long as connection string is considered, current recommendations are to put them in web.config or app.config (connectionStrings section)and then encrypt that section using built-in APIs which internally use DPAPI - Data Protection API - Many choose not to follow this step.
Regards,
Chinmay.