|
ms
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
getting to know c#Hello. I have been designated at work to convert MS Access databases (front
end only as back ends are on SQL Server) over to webapps using C#. I am excited about this task and realize the learning curve is going to going straight up. My concern is learning, grasping, comprehending the C# language. My experience is mainly in VBA use in Access and Excel. So, I guess my question is what others in this group did or recommend books, vids, tutorials, etc that I could use to learn C#? Anything is appreciated since I am starting practically with nothing as it is. Do have Visual Studio 2008 Pro, so at least it's a start. Thanks for your time and recommendations and suggestions. .... John On 6/30/2009 8:51 PM, JohnE wrote:
> Hello. I have been designated at work to convert MS Access databases (front Don't expect a straight up learning curve unless your time tick marks are in > end only as back ends are on SQL Server) over to webapps using C#. I am > excited about this task and realize the learning curve is going to going > straight up. My concern is learning, grasping, comprehending the C# > language. My experience is mainly in VBA use in Access and Excel. > > So, I guess my question is what others in this group did or recommend books, > vids, tutorials, etc that I could use to learn C#? Anything is appreciated > since I am starting practically with nothing as it is. Do have Visual Studio > 2008 Pro, so at least it's a start. > years :) it'll take some serious time and effort. Not only do you need to learn the language, you need to learn the .NET Framework as well. Personally, I like books published under O'Reilly and Apress. The Head First series of books are good as well. I would start with a .NET 3.5 book and a Programming C# (at least 3.0) book. Keep in mind C#4.0 is right around the corner. Cookbook's are useful as well. If you're going to be programming web applications, the .NETty thing's that you're going to need are: - SilverLight/WPF/XAML - WCF - LINQ Hopefully MS will get this NG working soon, because this is a very helpful community too. Best of luck, Bill IF there is a local community college in your area - the college will
usually have some comsc (computer science) course which would include C/C++/Java/VB. I took all the C/C++/MFC courses years back thinking I would never need it - until I started having to migrate stuff to C# (just like you). The majority of Microsoft development stuff is based on C/C++/MFC. So I would recommend getting a good grasp of the fundamentals in C/C++ at a community college (or university if money is not an object) where you have an instructor who can explain stuff in some depth. C# is pretty much a fancier (way easier to use) version of C/C++/MFC and managed (so you don't have to deal with malloc and calloc... from what little I remember of my C/C++ days - maybe not quite as low level). I would have had a much more difficult time in the migration process from VB to C# if I did not at least have C/C++ in the background somewhere. Rich *** Sent via Developersdex http://www.developersdex.com *** C# is the least of the problems. The data model is not the same (disconected
"recordsets" are a little bit different than the continuously connected ones that Access uses), and if you really mean "web application", may be you are better to take a look to ASP-net. The data-binding is also left to you for a much larger part, mainly if you have to use a lot a one-to-many relations, but if you mainly look to ONLY display information, then LINQ is probably a nice way to explore. If your backend is MS SQL Server, then you don't have the problem to remove the VBA user defined functions from your queries... but you are using queries, right? not loop over recordset? I often compare Access to a Dell computer, and C# with a computer you built yourself: Access made a lot of decisions for you, but present a set of techniques that are inter-compatible, and you have no hard decision left to make, while with C# you have access to a lot of possibilities, but some may not be as compatible for your needs as you would expect, or which requires pieces of code here and there to bridge the different 'components' of your system. But in the end, YOU may be able to acheive more with C# (the limiting factor being you, your time, your ressources, not C#). Vanderghast, Access MVP Show quoteHide quote "JohnE" <Jo***@discussions.microsoft.com> wrote in message news:06C9E009-B0CC-431A-A98E-36F2B31EC28D@microsoft.com... > Hello. I have been designated at work to convert MS Access databases > (front > end only as back ends are on SQL Server) over to webapps using C#. I am > excited about this task and realize the learning curve is going to going > straight up. My concern is learning, grasping, comprehending the C# > language. My experience is mainly in VBA use in Access and Excel. > > So, I guess my question is what others in this group did or recommend > books, > vids, tutorials, etc that I could use to learn C#? Anything is > appreciated > since I am starting practically with nothing as it is. Do have Visual > Studio > 2008 Pro, so at least it's a start. > > Thanks for your time and recommendations and suggestions. > > ... John "JohnE" <Jo***@discussions.microsoft.com> wrote in message The best advice I can give you is to forget completely any thoughts of news:06C9E009-B0CC-431A-A98E-36F2B31EC28D@microsoft.com... > I have been designated at work to convert MS Access databases (front > end only as back ends are on SQL Server) over to webapps using C#. > > Thanks for your time and recommendations and suggestions. "conversion". Access apps have so little in common with browser-based apps that any conversion attempt would just be a waste of time. You are 100% correct about the learning curve. However, only a small proportion of it will be actually learning C# - the main task will be to get your mindset into the .NET Framework way of doing things. I suggest you get a copy of this: http://www.amazon.co.uk/Beginning-ASP-NET-3-5-2008-Professional/dp/1590598911/ref=sr_1_1?ie=UTF8&s=books&qid=1246543023&sr=8-1 and work your way all the way through it from beginning to end. Once you've done that, and not before, then start thinking about how to create new web-based apps in ASP.NET which meet your current business requirements. By all means refer to the existing Access apps as a cross-check, but nothing more. And, when you need ASP.NET help in the future, the correct newsgroup is microsoft.public.dotnet.framework.aspnet > You are 100% correct about the learning curve. However, only a small I'd disagree with this. I'd say learning to use C# properly is going to be a > proportion of it will be actually learning C# - the main task will be to > get your mindset into the .NET Framework way of doing things. > massive learning curve for someone used to using VBA. The easy part is using the framework libraries. As we all know, one thing about a well designed library is its ease of use, and I'd say the .NET Framework is pretty well designed (at least most of it). Show quoteHide quote "Mark Rae [MVP]" <mark@markNOSPAMrae.net> wrote in message news:u13rp4x%23JHA.2872@TK2MSFTNGP05.phx.gbl... > "JohnE" <Jo***@discussions.microsoft.com> wrote in message > news:06C9E009-B0CC-431A-A98E-36F2B31EC28D@microsoft.com... > >> I have been designated at work to convert MS Access databases (front >> end only as back ends are on SQL Server) over to webapps using C#. >> >> Thanks for your time and recommendations and suggestions. > > The best advice I can give you is to forget completely any thoughts of > "conversion". Access apps have so little in common with browser-based apps > that any conversion attempt would just be a waste of time. > > You are 100% correct about the learning curve. However, only a small > proportion of it will be actually learning C# - the main task will be to > get your mindset into the .NET Framework way of doing things. > > I suggest you get a copy of this: > http://www.amazon.co.uk/Beginning-ASP-NET-3-5-2008-Professional/dp/1590598911/ref=sr_1_1?ie=UTF8&s=books&qid=1246543023&sr=8-1 > and work your way all the way through it from beginning to end. > > Once you've done that, and not before, then start thinking about how to > create new web-based apps in ASP.NET which meet your current business > requirements. By all means refer to the existing Access apps as a > cross-check, but nothing more. > > And, when you need ASP.NET help in the future, the correct newsgroup is > microsoft.public.dotnet.framework.aspnet > > > -- > Mark Rae > ASP.NET MVP > http://www.markrae.net Thanks to the 4 of you for responding. Each suggestion will be given
consideration. .... John Show quoteHide quote "JohnE" wrote: > Hello. I have been designated at work to convert MS Access databases (front > end only as back ends are on SQL Server) over to webapps using C#. I am > excited about this task and realize the learning curve is going to going > straight up. My concern is learning, grasping, comprehending the C# > language. My experience is mainly in VBA use in Access and Excel. > > So, I guess my question is what others in this group did or recommend books, > vids, tutorials, etc that I could use to learn C#? Anything is appreciated > since I am starting practically with nothing as it is. Do have Visual Studio > 2008 Pro, so at least it's a start. > > Thanks for your time and recommendations and suggestions. > > ... John  
Other interesting topics
set location of Form2 based on Location of Form1?
OT: missing posts Linq to Sql Exception Specified cast is not valid LINQ Max Linq to Sql insert fails check console args C# Export Excel to client side Application configuration settings - Do I make global? Remoting, how to create the remote server How to find out what the server name is? |
|||||||||||||||||||||||
