Hi,
Can anyone provide a good website for developing .NET (C#, both ASP.NET and WinForms) in an enterprise environment?
Currently the development I do is maintaining our hacked together CRM system, there is nothing in place to support it, no documentation, no code commenting, no procedures in place or anything. It is literally a case of backup the existing files, and copy over replacement ones when there are updates.
I have been asked to start a new project which would involve creating an application from scratch. I want to make sure it is done correctly, as there is a culture for blaming the developers of the product we sell for every bug or oversight, also I don't want to leave an unmaintainable application with nothing supporting it for someone else, like the CRM application was left for me.
So whilst I have no problem actually writing applications, and I have made many for my personal use, I don't have any experience in how things would be done differently when working in a development team.
I was taught the whole Analysis, Design, Specification side of things at Uni, and whilst I won't go into much detail, I will write a few pages on it's design (it's a relatively small application).
But it would be helpful if there is a website which can list and give an overview of the "extra mile" stuff which sits between the core programming and the formal documentation, for example:
Can anyone provide a good website for developing .NET (C#, both ASP.NET and WinForms) in an enterprise environment?
Currently the development I do is maintaining our hacked together CRM system, there is nothing in place to support it, no documentation, no code commenting, no procedures in place or anything. It is literally a case of backup the existing files, and copy over replacement ones when there are updates.
I have been asked to start a new project which would involve creating an application from scratch. I want to make sure it is done correctly, as there is a culture for blaming the developers of the product we sell for every bug or oversight, also I don't want to leave an unmaintainable application with nothing supporting it for someone else, like the CRM application was left for me.
So whilst I have no problem actually writing applications, and I have made many for my personal use, I don't have any experience in how things would be done differently when working in a development team.
I was taught the whole Analysis, Design, Specification side of things at Uni, and whilst I won't go into much detail, I will write a few pages on it's design (it's a relatively small application).
But it would be helpful if there is a website which can list and give an overview of the "extra mile" stuff which sits between the core programming and the formal documentation, for example:
- XML comments before a method which are used by IntelliSense to explain what it is doing, and what the parameters are.
- Proper debug code (not just "print("i am here now")") but making use of the Debug class.
- Possibly other ways to provide debug information whilst the application is running and the Visual Studio debugger is not attached to it.
- Good comments in the code to explain what is happening.
