Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Where to start?</p> <ol> <li>Choose a development environment (I would suggest Visual Studio 2008 Express or Professional, depending on the budget and the need for features of the Professional version)</li> <li>Even for one single developer: <strong>choose a Version control system !!!!</strong> (Subversion has only little administrative overhead, fine for one developer)</li> <li>Choose a .NET Framework version (3.5 is fine unless your application has to run on Win2K; for Win2K use .NET 2.0)</li> <li>Choose a mature programming language (C# or VB.NET, what you or your boss likes best)</li> <li>Choose a GUI technology (for a single developer, I would suggest using WinForms, unless you are going to write a Web application or a command line utility)</li> <li>Choose a mature DB access technology (ADO.NET works for a lot of things, unless you have very high performance requirements that are better dealt with old ADO/OleDB or DAO)</li> <li><em>EDIT</em>: use Google to find some entry examples according to the choosen technology, or buy yourself a book. For example, <a href="http://msdn.microsoft.com/en-us/library/aa288452%28VS.71%29.aspx" rel="nofollow noreferrer">here</a> is one for C# using OLE DB to access a MS Access DB. <a href="http://www.mvps.org/access/" rel="nofollow noreferrer">This Access site</a> is a good starting point, too.</li> <li><em>EDIT2</em>: make yourself familiar with "Microsoft Access" (the Office Application). Not because you are going to use it like a typical user, but you will probably need it for administrative purposes. And the VBA &amp; SQL documentation included will be sometimes helpful, even if you code with C# or VB.NET</li> <li><p><em>EDIT3</em>: for reporting purposes, choose a reporting technology. There are plenty of possibilites here, depending on your needs, your skills and/or budget, for example </p> <ul> <li>Plain ASCII or CSV reports (coded by hand)</li> <li>HTML or XML reports </li> <li>using Excel as reporting engine</li> <li>using a PDF library like <a href="http://sourceforge.net/projects/report/" rel="nofollow noreferrer">Report.NET</a></li> <li>using a third party tool like Crystal Reports</li> </ul> <p>You will find a lot of helpful links when you give <em>"report generation .net"</em> to Google, for example <a href="http://www.c-sharpcorner.com/UploadFile/harishps/ReportsInDotNet11082005233222PM/ReportsInDotNet.aspx" rel="nofollow noreferrer">this one</a>.</p></li> </ol> <p>And finally: come back to SO and ask more concrete questions when you come to the point where you have them.</p> <p>There might be other constraints, depending on what code is already existing in your organization. And I would avoid technologies like <code>F#</code>, WPF or <em>Linq to Entities</em>.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload