Marcus, Scott (GEAE, Contractor)
scott.marcus at ae.ge.com
Mon Jul 28 12:00:04 CDT 2003
John, Thanks for your optimism on .Net. All I ever here are negative things about MS products (which I make my living with). It is a good point you make about being on the leading edge. I think the same way. I just get discouraged cause very few tend to agree with that statement. It seems that most think that software development will eventually be all off shore. I say that moving off shore totally won't happen (small business needs physical presence). JM2C Scott -----Original Message----- From: jcolby at colbyconsulting.com [mailto:jcolby at colbyconsulting.com] Sent: Monday, July 28, 2003 12:49 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD]OT: C# was no-ip.com Scott, >My only doubts about .Net is that I'm not seeing very many job postings for .Net developers (but allot more than Access development). I am seeing more and more .net openings, at least more and more "ya need the kitchen sink and oh, by the way, ya need .net too" ads. I get the feeling that not many companies really understand it yet - momentum. However my feelings are that MS has spent a TON of money on developing the concept, and are pushing .net big time. If they put their muscle behind it, it won't be long till it's a "requirement" to get a job and I want to be on the leading edge of this one. PLUS, the .net framework is truly impressive in the capability it gives me "out of the box". >You must have read the same article as me (actually editors comments). I'm leaning VB.Net first and then adding C# to my skills. Seems silly to me that C# pulls in more money. Yea, it is silly considering the reality of the new .net environment. I'm betting that it won't be long before managers start to listen to M$ saying that any language is equally capable and stop paying more for C#. There are still a very small handful of indirection capabilities that C# has that VB doesn't, and if you need them then fine, go there. Otherwise VB is probably faster to get something up and running in. And finally, no, my framework has no equivalents in .net for the simple reason that my framework is about making form development in Access easier (even more RAD). Since .net is so very different from Access, much of what I do simply doesn't even make sense in .net. For example, I have a function in my framework that keeps a record selector combo synced to the form (bound) and the form synced to the combo. It turns out that in .net if you set the form (or a data grid) and a combo to the same dataset, selecting a record in the combo will just cause the two things to stay in sync (be on the same record). AFAICT, that is because the combo actually sets a "current record" property in the dataset object. Another example, in my framework I want to prevent the user from moving into a subform if the main form goes to the new record. .Net doesn't even HAVE subforms. Things like that. I am in the process of rewriting something that would "make sense" to port - my Sysvars. Assuming that I leave my error handlers in place, that port is really fairly straightforward. However I don't really have much hope of "just porting" my framework. In the end though, there is enough work to be done making .net as "database friendly" as Access that I am sure I will have plenty of similar projects. John W. Colby www.colbyconsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Marcus, Scott (GEAE, Contractor) Sent: Monday, July 28, 2003 12:03 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD]OT: C# was no-ip.com John, You must have read the same article as me (actually editors comments). I'm leaning VB.Net first and then adding C# to my skills. Seems silly to me that C# pulls in more money. Like you, that is why I'm going to learn it also. Have you seen any silly job postings like "C# developer with 5 years experience..."? Have you found that your Access framework already has equivalents in .Net framework? I'm not far enough into .Net to have an opinion yet. I can say that if it is similar to how Java works, I won't like it. I hear that C# is very close to Java. What I've learned in VB.Net so far seems pretty straight forward. My only doubts about .Net is that I'm not seeing very many job postings for .Net developers (but allot more than Access development). Scott -----Original Message----- From: jcolby at colbyconsulting.com [mailto:jcolby at colbyconsulting.com] Sent: Monday, July 28, 2003 11:47 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD]OT: C# was no-ip.com Scott, Not yet, though I think I will end up there. I'm thinking that learning VB.Net and more importantly the .net framework FIRST will be most useful to me. The framework is massive and being comfortable with that is a requirement regardless of the language you then use for your programming. Once that is done I will probably move to C# for the simple reason that the polls indicate C# programmers get better money. I did a controller project down in Mexico in a custom 'C' language so it isn't totally foreign. Again though, the whole point of the .Net concept is that the framework really provides about 90% of the functionality and it is used EXACTLY the same regardless of the language you use. The language itself is really a thin veneer over the top of the framework. Even things like variables are framework objects so that any .net language can literally pass their variables back and forth without the silly problems like you see with VB and C not treating strings the same way. John W. Colby www.colbyconsulting.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com