Re: CORS, Azure, Chrome desktop and mobile
as you see from the responses for the thread, all of us are working just fine. if its the network admin's decision to intentionally block web requests then its their issue, not developers'. Your app is fine. time to throw the ball - there is nothing you can do as a developer around specific firewall rules of different networks On 13 October 2015 at 17:07, David Burstin wrote: > Firstly, thanks again to everyone who has taken the time to look at this. > > Yes, it turns out that it is a firewall issue. :( > > So, given that having a web page talk to a web service at a different > origin is not a crazy or unusual situation, how do you guys deal with this? > How do you make the web page work, given that you can't go to everyone who > looks at your site and ask them to change their firewall rules, no matter > how dumb they are (the firewall rules and the people you are talking to)? > > Or is it just not possible? > > Cheers > Dave > > On 13 October 2015 at 16:53, Thomas Koster wrote: > >> On 13 October 2015 at 15:39, David Burstin >> wrote: >> > My response headers don't have "Access-Control-Allow-Origin". Any ideas >> > why? (I am about to hit google) >> >> On 13 October 2015 at 16:11, Thomas Koster wrote: >> > Are you using a proxy, firewall or browser plugin that is removing them? >> > If you suspect this, try HTTPS (although a browser plugin can still bite >> > you). >> >> On 13 October 2015 at 16:15, David Burstin >> wrote: >> > Thanks Thomas. Definitely not a plugin, possibly a proxy or firewall >> issue. >> > I will talk to the guys here who know more about this than me. >> >> At first, looking at your screenshot, I didn't think that a proxy or >> firewall was removing headers because outgoing headers look fine and >> rubbish headers like "X-Powered-By" did make it through. (Why include >> "X-Powered-By" on a whitelist but not CORS headers?!). But then I >> noticed that "X-AspNet-Version" is also missing from your >> screenshot... >> >> -- >> Thomas Koster >> > >
Re: CORS, Azure, Chrome desktop and mobile
Firstly, thanks again to everyone who has taken the time to look at this. Yes, it turns out that it is a firewall issue. :( So, given that having a web page talk to a web service at a different origin is not a crazy or unusual situation, how do you guys deal with this? How do you make the web page work, given that you can't go to everyone who looks at your site and ask them to change their firewall rules, no matter how dumb they are (the firewall rules and the people you are talking to)? Or is it just not possible? Cheers Dave On 13 October 2015 at 16:53, Thomas Koster wrote: > On 13 October 2015 at 15:39, David Burstin > wrote: > > My response headers don't have "Access-Control-Allow-Origin". Any ideas > > why? (I am about to hit google) > > On 13 October 2015 at 16:11, Thomas Koster wrote: > > Are you using a proxy, firewall or browser plugin that is removing them? > > If you suspect this, try HTTPS (although a browser plugin can still bite > > you). > > On 13 October 2015 at 16:15, David Burstin > wrote: > > Thanks Thomas. Definitely not a plugin, possibly a proxy or firewall > issue. > > I will talk to the guys here who know more about this than me. > > At first, looking at your screenshot, I didn't think that a proxy or > firewall was removing headers because outgoing headers look fine and > rubbish headers like "X-Powered-By" did make it through. (Why include > "X-Powered-By" on a whitelist but not CORS headers?!). But then I > noticed that "X-AspNet-Version" is also missing from your > screenshot... > > -- > Thomas Koster >
Re: CORS, Azure, Chrome desktop and mobile
On 13 October 2015 at 15:39, David Burstin wrote: > My response headers don't have "Access-Control-Allow-Origin". Any ideas > why? (I am about to hit google) On 13 October 2015 at 16:11, Thomas Koster wrote: > Are you using a proxy, firewall or browser plugin that is removing them? > If you suspect this, try HTTPS (although a browser plugin can still bite > you). On 13 October 2015 at 16:15, David Burstin wrote: > Thanks Thomas. Definitely not a plugin, possibly a proxy or firewall issue. > I will talk to the guys here who know more about this than me. At first, looking at your screenshot, I didn't think that a proxy or firewall was removing headers because outgoing headers look fine and rubbish headers like "X-Powered-By" did make it through. (Why include "X-Powered-By" on a whitelist but not CORS headers?!). But then I noticed that "X-AspNet-Version" is also missing from your screenshot... -- Thomas Koster
Re: CORS, Azure, Chrome desktop and mobile
Thanks Thomas. Definitely not a plugin, possibly a proxy or firewall issue. I will talk to the guys here who know more about this than me. On 13 October 2015 at 16:11, Thomas Koster wrote: > On 13 October 2015 at 15:39, David Burstin > wrote: > >> My response headers don't have "Access-Control-Allow-Origin". Any ideas >> why? (I am about to hit google) >> > > Are you using a proxy, firewall or browser plugin that is removing them? > If you suspect this, try HTTPS (although a browser plugin can still bite > you). > > -- > Thomas Koster > >
Re: CORS, Azure, Chrome desktop and mobile
On 13 October 2015 at 15:39, David Burstin wrote: > My response headers don't have "Access-Control-Allow-Origin". Any ideas > why? (I am about to hit google) > Are you using a proxy, firewall or browser plugin that is removing them? If you suspect this, try HTTPS (although a browser plugin can still bite you). -- Thomas Koster
Re: CORS, Azure, Chrome desktop and mobile
Thanks everyone for having a look. I will try from a different network, as other machines here are getting the same result (fail). On 13 October 2015 at 15:29, ILT wrote: > David, the only error I have is that favicon.ico can’t be found by server. > > Chrome Version 45.0.2454.101 m, Windows 7 Ultimate 64-bit, .NET 4.52 > -- > > Ian Thomas > Albert Park, Victoria > > > > *From:* ozdotnet-boun...@ozdotnet.com [mailto: > ozdotnet-boun...@ozdotnet.com] *On Behalf Of *David Burstin > *Sent:* Tuesday, October 13, 2015 2:58 PM > *To:* ozDotNet > *Subject:* Re: CORS, Azure, Chrome desktop and mobile > > > > Here is mine on Chrome 45, Windows 7: > > > > [image: Inline images 1] > > > > There should be a list of items on the page. Note the error message in > chrome tools. > > > > On 13 October 2015 at 14:46, Nelson wrote: > > Works for me - win7 chrome 45 > > > > details on how to trigger the error maybe? > > > > or attach your error log > > > > On 13 October 2015 at 14:42, David Burstin > wrote: > > Hi folks, > > > > I have a web site on Azure and it utilizes a web api on Azure. I believe > that I have set up CORS correctly (controller attributes in web api), but I > still get errors when using Chrome from the desktop, although Chrome from > Android has no problems. > > > > Does anyone have any ideas how to fix / debug this? > > > > It is just a play site, so if you want to test it go to > http://dartsstuff.azurewebsites.net/ > > > > Cheers > > Dave > > > > >
RE: CORS, Azure, Chrome desktop and mobile
David, the only error I have is that favicon.ico can’t be found by server. Chrome Version 45.0.2454.101 m, Windows 7 Ultimate 64-bit, .NET 4.52 _ Ian Thomas Albert Park, Victoria From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of David Burstin Sent: Tuesday, October 13, 2015 2:58 PM To: ozDotNet Subject: Re: CORS, Azure, Chrome desktop and mobile Here is mine on Chrome 45, Windows 7: Inline images 1 There should be a list of items on the page. Note the error message in chrome tools. On 13 October 2015 at 14:46, Nelson wrote: Works for me - win7 chrome 45 details on how to trigger the error maybe? or attach your error log On 13 October 2015 at 14:42, David Burstin wrote: Hi folks, I have a web site on Azure and it utilizes a web api on Azure. I believe that I have set up CORS correctly (controller attributes in web api), but I still get errors when using Chrome from the desktop, although Chrome from Android has no problems. Does anyone have any ideas how to fix / debug this? It is just a play site, so if you want to test it go to http://dartsstuff.azurewebsites.net/ Cheers Dave
Re: CORS, Azure, Chrome desktop and mobile
Here is mine on Chrome 45, Windows 7: [image: Inline images 1] There should be a list of items on the page. Note the error message in chrome tools. On 13 October 2015 at 14:46, Nelson wrote: > Works for me - win7 chrome 45 > > details on how to trigger the error maybe? > > or attach your error log > > On 13 October 2015 at 14:42, David Burstin > wrote: > >> Hi folks, >> >> I have a web site on Azure and it utilizes a web api on Azure. I believe >> that I have set up CORS correctly (controller attributes in web api), but I >> still get errors when using Chrome from the desktop, although Chrome from >> Android has no problems. >> >> Does anyone have any ideas how to fix / debug this? >> >> It is just a play site, so if you want to test it go to >> http://dartsstuff.azurewebsites.net/ >> >> Cheers >> Dave >> > >
Re: CORS, Azure, Chrome desktop and mobile
Works for me - win7 chrome 45 details on how to trigger the error maybe? or attach your error log On 13 October 2015 at 14:42, David Burstin wrote: > Hi folks, > > I have a web site on Azure and it utilizes a web api on Azure. I believe > that I have set up CORS correctly (controller attributes in web api), but I > still get errors when using Chrome from the desktop, although Chrome from > Android has no problems. > > Does anyone have any ideas how to fix / debug this? > > It is just a play site, so if you want to test it go to > http://dartsstuff.azurewebsites.net/ > > Cheers > Dave >
CORS, Azure, Chrome desktop and mobile
Hi folks, I have a web site on Azure and it utilizes a web api on Azure. I believe that I have set up CORS correctly (controller attributes in web api), but I still get errors when using Chrome from the desktop, although Chrome from Android has no problems. Does anyone have any ideas how to fix / debug this? It is just a play site, so if you want to test it go to http://dartsstuff.azurewebsites.net/ Cheers Dave
RE: vb.net
There’s also the new bling bling oh look shiny (squirrel) approach, versus the existing and established client base and app approach. Pumping out new apps using the latest buts just shows you’re good at playing with new toys. Improving, expanding, and working with real user bases, develops problem solving and people skills. I’ve worked on apps where we’ve moved existing clients to web based solutions and had to deal with client expectations to have the same keyboard shortcuts, wanting similar screens to their old vt100 emulation screens (well nit that bad, but not far from it). Some do view that as a pain, but clients who have to pay for the changes are the ones who find it most painful if the change is just for change sake. Learning how to work effectively with existing clients and codebase will develop real skills you can’t get elsewhere. If you want to code with the latest bits pushing out only new stuff, you can do that with the internet and your spare time 😏 Btw: reporting services custom code... just sating😉 From: David Burstin Sent: Tuesday, 13 October 2015 2:19 PM To: ozDotNet Subject: Re: vb.net I think the real message here is - forget the language, just don't work for Nelson's senior. Stubborn a**h are not confined to any particular language. :) On 13 October 2015 at 14:14, Nelson wrote: My concern here (regarding the job offer) is not about the language use. i cannot stress enough how a pain in the a** it can be when working with seniors who are reluctant to change and adopt newer better technology. And as a Junior in the team you are basically screwed, especially you started your training with all the modern tech and tools. I had a hard time convincing my senior to switch to ASP.NET MVC from WebForms. although that turn out may not be the best idea - he still code like WebForms way in MVC anyway he still thinks WebForms is superior and can do stuff MVC cant do till this date unfortunately you can also imagine how your ideas got banned just because you are the junior and he play the experience game with you. even though that experience translate to sticking to 10-20 years old libraries when there are modern, much more popular alternatives (the best example i think of right now is that he is still using his copy of a 1997 alpha version of date.js library - probably thats the time he started learning js?) I'm not saying VB.NET people are all stubborn and old. but the probability of having to work with a**h*** is just much higher than i like. After all, it won't be a cultural fit for me personally as i'm a state-of-the-art person and would love to work with new technology On 13 October 2015 at 13:53, Bill McCarthy wrote: Although there’s lots of c ‘style’ languages, the devil is always in the details/differences. I find it hard to switch between c# and js and not forget/mess up. With vb.net and js not so much a problem. The same use to be said for vb and vbscript in days of asp From: David Burstin Sent: Tuesday, 13 October 2015 1:41 PM To: ozDotNet Subject: Re: vb.net I started my .net journey with vb.net, but these days I code C# unless I have to use vb for working with a legacy system. I agree with Bill - there really isn't much difference between using the languages in .net. In fact, knowing my way around the .net framework (from having used it with vb) made the transition to c# much easier. BUT, outside the .net world, I have found my knowledge of C# has helped me in reading (and learning) other languages - eg java, js, ruby. These all have a syntax which is far more like c# than vb. So, if you can only use one language, for me it would be C# - but there is no reason at all that you should be confined to one language. If you are interested in the job, than go for it. Whatever happens, you will learn. Any job provides an opportunity to practice our craft and become better programmers. Plus, you can do projects after hours in whatever language you want :) Cheers Dave On 13 October 2015 at 13:33, Bill McCarthy wrote: This usually a great rant starter for a Friday conversation. Realistically though Vb.net is much a muchness with c# on .net. Definitely the best language if doing integrated xml. With late binding stuff it has some advantages with better conversions, but also disadvantages such as wider scope. Realistically the biggest disadvantage of vb.net is if you want to integrate some large source code from open licence stuff... usually more is available in c#. From: Tom P Sent: Tuesday, 13 October 2015 12:48 PM To: ozDotNet Subject: vb.net Guys I've been offered a junior dev job but they insist on vb.net only. Does anyone know what is happening with vb.net going forward? I would hate to get stuck into the vb.net world and have it killed off within a few years. Thanks Tom
Re: vb.net
Thanks guys some really good advice here. I will give it a shot with positivity. Thanks Tom On Tuesday, 13 October 2015, David Burstin wrote: > I think the real message here is - forget the language, just don't work > for Nelson's senior. Stubborn a**h are not confined to any particular > language. :) > > On 13 October 2015 at 14:14, Nelson > wrote: > >> My concern here (regarding the job offer) is not about the language use. >> >> i cannot stress enough how a pain in the a** it can be when working with >> seniors who are reluctant to change and adopt newer better technology. >> >> And as a Junior in the team you are basically screwed, especially you >> started your training with all the modern tech and tools. >> >> >> >> I had a hard time convincing my senior to switch to ASP.NET MVC from >> WebForms. >> >> although that turn out may not be the best idea - he still code like >> WebForms way in MVC >> >> anyway he still thinks WebForms is superior and can do stuff MVC cant do >> till this date unfortunately >> >> >> >> you can also imagine how your ideas got banned just because you are the >> junior and he play the experience game with you. >> >> even though that experience translate to sticking to 10-20 years old >> libraries when there are modern, much more popular alternatives >> >> (the best example i think of right now is that he is still using his copy >> of a 1997 alpha version of date.js library - probably thats the time he >> started learning js?) >> >> >> >> I'm not saying VB.NET people are all stubborn and old. but the >> probability of having to work with a**h*** is just much higher than i like. >> >> After all, it won't be a cultural fit for me personally as i'm a >> state-of-the-art person and would love to work with new technology >> >> >> On 13 October 2015 at 13:53, Bill McCarthy < >> bill.mccarthy.li...@live.com.au >> > wrote: >> >>> >>> >>> Although there’s lots of c ‘style’ languages, the devil is always in the >>> details/differences. I find it hard to switch between c# and js and not >>> forget/mess up. With vb.net and js not so much a problem. >>> >>> >>> >>> The same use to be said for vb and vbscript in days of asp >>> >>> >>> >>> >>> >>> >>> >>> >>> *From: *David Burstin >>> *Sent: *Tuesday, 13 October 2015 1:41 PM >>> *To: *ozDotNet >>> *Subject: *Re: vb.net >>> >>> >>> >>> >>> >>> I started my .net journey with vb.net, but these days I code C# unless >>> I have to use vb for working with a legacy system. >>> >>> >>> >>> I agree with Bill - there really isn't much difference between using the >>> languages in .net. In fact, knowing my way around the .net framework (from >>> having used it with vb) made the transition to c# much easier. >>> >>> >>> >>> BUT, outside the .net world, I have found my knowledge of C# has helped >>> me in reading (and learning) other languages - eg java, js, ruby. These all >>> have a syntax which is far more like c# than vb. >>> >>> >>> >>> So, if you can only use one language, for me it would be C# - but there >>> is no reason at all that you should be confined to one language. If you are >>> interested in the job, than go for it. Whatever happens, you will learn. >>> Any job provides an opportunity to practice our craft and become better >>> programmers. Plus, you can do projects after hours in whatever language you >>> want :) >>> >>> >>> >>> Cheers >>> >>> Dave >>> >>> >>> >>> On 13 October 2015 at 13:33, Bill McCarthy < >>> bill.mccarthy.li...@live.com.au >>> > >>> wrote: >>> >>> >>> >>> >>> >>> This usually a great rant starter for a Friday conversation. >>> Realistically though Vb.net is much a muchness with c# on .net. Definitely >>> the best language if doing integrated xml. With late binding stuff it has >>> some advantages with better conversions, but also disadvantages such as >>> wider scope. >>> >>> >>> >>> Realistically the biggest disadvantage of vb.net is if you want to >>> integrate some large source code from open licence stuff... usually more is >>> available in c#. >>> >>> >>> >>> >>> >>> >>> >>> >>> *From: *Tom P >>> *Sent: *Tuesday, 13 October 2015 12:48 PM >>> *To: *ozDotNet >>> *Subject: *vb.net >>> >>> >>> >>> >>> >>> Guys I've been offered a junior dev job but they insist on vb.net only. >>> Does anyone know what is happening with vb.net going forward? I would >>> hate to get stuck into the vb.net world and have it killed off within a >>> few years. >>> >>> >>> Thanks >>> >>> Tom >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> >> > -- Thanks Tom
Re: vb.net
I think the real message here is - forget the language, just don't work for Nelson's senior. Stubborn a**h are not confined to any particular language. :) On 13 October 2015 at 14:14, Nelson wrote: > My concern here (regarding the job offer) is not about the language use. > > i cannot stress enough how a pain in the a** it can be when working with > seniors who are reluctant to change and adopt newer better technology. > > And as a Junior in the team you are basically screwed, especially you > started your training with all the modern tech and tools. > > > > I had a hard time convincing my senior to switch to ASP.NET MVC from > WebForms. > > although that turn out may not be the best idea - he still code like > WebForms way in MVC > > anyway he still thinks WebForms is superior and can do stuff MVC cant do > till this date unfortunately > > > > you can also imagine how your ideas got banned just because you are the > junior and he play the experience game with you. > > even though that experience translate to sticking to 10-20 years old > libraries when there are modern, much more popular alternatives > > (the best example i think of right now is that he is still using his copy > of a 1997 alpha version of date.js library - probably thats the time he > started learning js?) > > > > I'm not saying VB.NET people are all stubborn and old. but the > probability of having to work with a**h*** is just much higher than i like. > > After all, it won't be a cultural fit for me personally as i'm a > state-of-the-art person and would love to work with new technology > > > On 13 October 2015 at 13:53, Bill McCarthy < > bill.mccarthy.li...@live.com.au> wrote: > >> >> >> Although there’s lots of c ‘style’ languages, the devil is always in the >> details/differences. I find it hard to switch between c# and js and not >> forget/mess up. With vb.net and js not so much a problem. >> >> >> >> The same use to be said for vb and vbscript in days of asp >> >> >> >> >> >> >> >> >> *From: *David Burstin >> *Sent: *Tuesday, 13 October 2015 1:41 PM >> *To: *ozDotNet >> *Subject: *Re: vb.net >> >> >> >> >> >> I started my .net journey with vb.net, but these days I code C# unless I >> have to use vb for working with a legacy system. >> >> >> >> I agree with Bill - there really isn't much difference between using the >> languages in .net. In fact, knowing my way around the .net framework (from >> having used it with vb) made the transition to c# much easier. >> >> >> >> BUT, outside the .net world, I have found my knowledge of C# has helped >> me in reading (and learning) other languages - eg java, js, ruby. These all >> have a syntax which is far more like c# than vb. >> >> >> >> So, if you can only use one language, for me it would be C# - but there >> is no reason at all that you should be confined to one language. If you are >> interested in the job, than go for it. Whatever happens, you will learn. >> Any job provides an opportunity to practice our craft and become better >> programmers. Plus, you can do projects after hours in whatever language you >> want :) >> >> >> >> Cheers >> >> Dave >> >> >> >> On 13 October 2015 at 13:33, Bill McCarthy < >> bill.mccarthy.li...@live.com.au> wrote: >> >> >> >> >> >> This usually a great rant starter for a Friday conversation. >> Realistically though Vb.net is much a muchness with c# on .net. Definitely >> the best language if doing integrated xml. With late binding stuff it has >> some advantages with better conversions, but also disadvantages such as >> wider scope. >> >> >> >> Realistically the biggest disadvantage of vb.net is if you want to >> integrate some large source code from open licence stuff... usually more is >> available in c#. >> >> >> >> >> >> >> >> >> *From: *Tom P >> *Sent: *Tuesday, 13 October 2015 12:48 PM >> *To: *ozDotNet >> *Subject: *vb.net >> >> >> >> >> >> Guys I've been offered a junior dev job but they insist on vb.net only. >> Does anyone know what is happening with vb.net going forward? I would >> hate to get stuck into the vb.net world and have it killed off within a >> few years. >> >> >> Thanks >> >> Tom >> >> >> >> >> >> >> >> >> >> >> > >
Re: vb.net
Definitely agree Bill. For some people (me), the similarities are helpful. For others (Bill), it is the differences that prevent confusion. Tom, see where you sit in relation to similarities / differences - self-awareness will definitely help your decision. On 13 October 2015 at 13:53, Bill McCarthy wrote: > > > Although there’s lots of c ‘style’ languages, the devil is always in the > details/differences. I find it hard to switch between c# and js and not > forget/mess up. With vb.net and js not so much a problem. > > > > The same use to be said for vb and vbscript in days of asp > > > > > > > > > *From: *David Burstin > *Sent: *Tuesday, 13 October 2015 1:41 PM > *To: *ozDotNet > *Subject: *Re: vb.net > > > > > > I started my .net journey with vb.net, but these days I code C# unless I > have to use vb for working with a legacy system. > > > > I agree with Bill - there really isn't much difference between using the > languages in .net. In fact, knowing my way around the .net framework (from > having used it with vb) made the transition to c# much easier. > > > > BUT, outside the .net world, I have found my knowledge of C# has helped me > in reading (and learning) other languages - eg java, js, ruby. These all > have a syntax which is far more like c# than vb. > > > > So, if you can only use one language, for me it would be C# - but there is > no reason at all that you should be confined to one language. If you are > interested in the job, than go for it. Whatever happens, you will learn. > Any job provides an opportunity to practice our craft and become better > programmers. Plus, you can do projects after hours in whatever language you > want :) > > > > Cheers > > Dave > > > > On 13 October 2015 at 13:33, Bill McCarthy < > bill.mccarthy.li...@live.com.au> wrote: > > > > > > This usually a great rant starter for a Friday conversation. Realistically > though Vb.net is much a muchness with c# on .net. Definitely the best > language if doing integrated xml. With late binding stuff it has some > advantages with better conversions, but also disadvantages such as wider > scope. > > > > Realistically the biggest disadvantage of vb.net is if you want to > integrate some large source code from open licence stuff... usually more is > available in c#. > > > > > > > > > *From: *Tom P > *Sent: *Tuesday, 13 October 2015 12:48 PM > *To: *ozDotNet > *Subject: *vb.net > > > > > > Guys I've been offered a junior dev job but they insist on vb.net only. > Does anyone know what is happening with vb.net going forward? I would > hate to get stuck into the vb.net world and have it killed off within a > few years. > > > Thanks > > Tom > > > > > > > > > > >
Re: vb.net
My concern here (regarding the job offer) is not about the language use. i cannot stress enough how a pain in the a** it can be when working with seniors who are reluctant to change and adopt newer better technology. And as a Junior in the team you are basically screwed, especially you started your training with all the modern tech and tools. I had a hard time convincing my senior to switch to ASP.NET MVC from WebForms. although that turn out may not be the best idea - he still code like WebForms way in MVC anyway he still thinks WebForms is superior and can do stuff MVC cant do till this date unfortunately you can also imagine how your ideas got banned just because you are the junior and he play the experience game with you. even though that experience translate to sticking to 10-20 years old libraries when there are modern, much more popular alternatives (the best example i think of right now is that he is still using his copy of a 1997 alpha version of date.js library - probably thats the time he started learning js?) I'm not saying VB.NET people are all stubborn and old. but the probability of having to work with a**h*** is just much higher than i like. After all, it won't be a cultural fit for me personally as i'm a state-of-the-art person and would love to work with new technology On 13 October 2015 at 13:53, Bill McCarthy wrote: > > > Although there’s lots of c ‘style’ languages, the devil is always in the > details/differences. I find it hard to switch between c# and js and not > forget/mess up. With vb.net and js not so much a problem. > > > > The same use to be said for vb and vbscript in days of asp > > > > > > > > > *From: *David Burstin > *Sent: *Tuesday, 13 October 2015 1:41 PM > *To: *ozDotNet > *Subject: *Re: vb.net > > > > > > I started my .net journey with vb.net, but these days I code C# unless I > have to use vb for working with a legacy system. > > > > I agree with Bill - there really isn't much difference between using the > languages in .net. In fact, knowing my way around the .net framework (from > having used it with vb) made the transition to c# much easier. > > > > BUT, outside the .net world, I have found my knowledge of C# has helped me > in reading (and learning) other languages - eg java, js, ruby. These all > have a syntax which is far more like c# than vb. > > > > So, if you can only use one language, for me it would be C# - but there is > no reason at all that you should be confined to one language. If you are > interested in the job, than go for it. Whatever happens, you will learn. > Any job provides an opportunity to practice our craft and become better > programmers. Plus, you can do projects after hours in whatever language you > want :) > > > > Cheers > > Dave > > > > On 13 October 2015 at 13:33, Bill McCarthy < > bill.mccarthy.li...@live.com.au> wrote: > > > > > > This usually a great rant starter for a Friday conversation. Realistically > though Vb.net is much a muchness with c# on .net. Definitely the best > language if doing integrated xml. With late binding stuff it has some > advantages with better conversions, but also disadvantages such as wider > scope. > > > > Realistically the biggest disadvantage of vb.net is if you want to > integrate some large source code from open licence stuff... usually more is > available in c#. > > > > > > > > > *From: *Tom P > *Sent: *Tuesday, 13 October 2015 12:48 PM > *To: *ozDotNet > *Subject: *vb.net > > > > > > Guys I've been offered a junior dev job but they insist on vb.net only. > Does anyone know what is happening with vb.net going forward? I would > hate to get stuck into the vb.net world and have it killed off within a > few years. > > > Thanks > > Tom > > > > > > > > > > >
RE: vb.net
Although there’s lots of c ‘style’ languages, the devil is always in the details/differences. I find it hard to switch between c# and js and not forget/mess up. With vb.net and js not so much a problem. The same use to be said for vb and vbscript in days of asp From: David Burstin Sent: Tuesday, 13 October 2015 1:41 PM To: ozDotNet Subject: Re: vb.net I started my .net journey with vb.net, but these days I code C# unless I have to use vb for working with a legacy system. I agree with Bill - there really isn't much difference between using the languages in .net. In fact, knowing my way around the .net framework (from having used it with vb) made the transition to c# much easier. BUT, outside the .net world, I have found my knowledge of C# has helped me in reading (and learning) other languages - eg java, js, ruby. These all have a syntax which is far more like c# than vb. So, if you can only use one language, for me it would be C# - but there is no reason at all that you should be confined to one language. If you are interested in the job, than go for it. Whatever happens, you will learn. Any job provides an opportunity to practice our craft and become better programmers. Plus, you can do projects after hours in whatever language you want :) Cheers Dave On 13 October 2015 at 13:33, Bill McCarthy wrote: This usually a great rant starter for a Friday conversation. Realistically though Vb.net is much a muchness with c# on .net. Definitely the best language if doing integrated xml. With late binding stuff it has some advantages with better conversions, but also disadvantages such as wider scope. Realistically the biggest disadvantage of vb.net is if you want to integrate some large source code from open licence stuff... usually more is available in c#. From: Tom P Sent: Tuesday, 13 October 2015 12:48 PM To: ozDotNet Subject: vb.net Guys I've been offered a junior dev job but they insist on vb.net only. Does anyone know what is happening with vb.net going forward? I would hate to get stuck into the vb.net world and have it killed off within a few years. Thanks Tom
Re: vb.net
I tend to agree with you. If there are two languages (C# & VB.NET) that are 99% functionally equivalent but 90% of people use one (C#) then to me it is a no brainer to use C# are well. I can't really think of any reason why someone would choose VB.NET for a new project over C# where the benefits outweigh the disadvantages. On Tue, Oct 13, 2015 at 1:35 PM, Nelson wrote: > things that are old enough to still be running vb? > > and i have a feeling people who still stick to vb are fairly stubborn. > > i know im stereotyping here sorry if i offended anyone but that was my > experience > > > On Tuesday, 13 October 2015, Bill McCarthy < > bill.mccarthy.li...@live.com.au> wrote: > >> Really ? What ‘legacy’ things are you referring to ? >> >> >> >> >> >> >> >> >> >> >> *From: *Nelson >> *Sent: *Tuesday, 13 October 2015 12:52 PM >> *To: *ozDotNet >> *Subject: *Re: vb.net >> >> >> >> >> >> Personally i would turn down such offer - actually wouldnt even be >> applying in the first place. >> >> >> >> pretty good market out there with JS and C# .NET, try looking else where >> if you can >> >> >> >> >> >> >> >> if you just recently graduated, your modern mindset would have a hard >> time dealing with VB and the legacy system. >> >> >> >> you will likely lose passion >> >> >> >> >> >> just my 2 cents >> >> >> >> >> >> On 13 October 2015 at 12:47, Tom P wrote: >> >> Guys I've been offered a junior dev job but they insist on vb.net only. >> Does anyone know what is happening with vb.net going forward? I would >> hate to get stuck into the vb.net world and have it killed off within a >> few years. >> >> >> Thanks >> >> Tom >> >> >> >> >> >> >> >
RE: vb.net
Tom said ‘vb.net’. From: Nelson Sent: Tuesday, 13 October 2015 1:35 PM To: Bill McCarthy Cc: Nelson;ozDotNet Subject: Re: vb.net things that are old enough to still be running vb? and i have a feeling people who still stick to vb are fairly stubborn. i know im stereotyping here sorry if i offended anyone but that was my experience On Tuesday, 13 October 2015, Bill McCarthy wrote: Really ? What ‘legacy’ things are you referring to ? From: Nelson Sent: Tuesday, 13 October 2015 12:52 PM To: ozDotNet Subject: Re: vb.net Personally i would turn down such offer - actually wouldnt even be applying in the first place. pretty good market out there with JS and C# .NET, try looking else where if you can if you just recently graduated, your modern mindset would have a hard time dealing with VB and the legacy system. you will likely lose passion just my 2 cents On 13 October 2015 at 12:47, Tom P wrote: Guys I've been offered a junior dev job but they insist on vb.net only. Does anyone know what is happening with vb.net going forward? I would hate to get stuck into the vb.net world and have it killed off within a few years. Thanks Tom
Re: vb.net
I started my .net journey with vb.net, but these days I code C# unless I have to use vb for working with a legacy system. I agree with Bill - there really isn't much difference between using the languages in .net. In fact, knowing my way around the .net framework (from having used it with vb) made the transition to c# much easier. BUT, outside the .net world, I have found my knowledge of C# has helped me in reading (and learning) other languages - eg java, js, ruby. These all have a syntax which is far more like c# than vb. So, if you can only use one language, for me it would be C# - but there is no reason at all that you should be confined to one language. If you are interested in the job, than go for it. Whatever happens, you will learn. Any job provides an opportunity to practice our craft and become better programmers. Plus, you can do projects after hours in whatever language you want :) Cheers Dave On 13 October 2015 at 13:33, Bill McCarthy wrote: > > > > > This usually a great rant starter for a Friday conversation. Realistically > though Vb.net is much a muchness with c# on .net. Definitely the best > language if doing integrated xml. With late binding stuff it has some > advantages with better conversions, but also disadvantages such as wider > scope. > > > > Realistically the biggest disadvantage of vb.net is if you want to > integrate some large source code from open licence stuff... usually more is > available in c#. > > > > > > > > > *From: *Tom P > *Sent: *Tuesday, 13 October 2015 12:48 PM > *To: *ozDotNet > *Subject: *vb.net > > > > > > Guys I've been offered a junior dev job but they insist on vb.net only. > Does anyone know what is happening with vb.net going forward? I would > hate to get stuck into the vb.net world and have it killed off within a > few years. > > > Thanks > > Tom > > > > >
Re: vb.net
things that are old enough to still be running vb? and i have a feeling people who still stick to vb are fairly stubborn. i know im stereotyping here sorry if i offended anyone but that was my experience On Tuesday, 13 October 2015, Bill McCarthy wrote: > Really ? What ‘legacy’ things are you referring to ? > > > > > > > > > > > *From: *Nelson > *Sent: *Tuesday, 13 October 2015 12:52 PM > *To: *ozDotNet > *Subject: *Re: vb.net > > > > > > Personally i would turn down such offer - actually wouldnt even be > applying in the first place. > > > > pretty good market out there with JS and C# .NET, try looking else where > if you can > > > > > > > > if you just recently graduated, your modern mindset would have a hard time > dealing with VB and the legacy system. > > > > you will likely lose passion > > > > > > just my 2 cents > > > > > > On 13 October 2015 at 12:47, Tom P > wrote: > > Guys I've been offered a junior dev job but they insist on vb.net only. > Does anyone know what is happening with vb.net going forward? I would > hate to get stuck into the vb.net world and have it killed off within a > few years. > > > Thanks > > Tom > > > > > > >
RE: vb.net
This usually a great rant starter for a Friday conversation. Realistically though Vb.net is much a muchness with c# on .net. Definitely the best language if doing integrated xml. With late binding stuff it has some advantages with better conversions, but also disadvantages such as wider scope. Realistically the biggest disadvantage of vb.net is if you want to integrate some large source code from open licence stuff... usually more is available in c#. From: Tom P Sent: Tuesday, 13 October 2015 12:48 PM To: ozDotNet Subject: vb.net Guys I've been offered a junior dev job but they insist on vb.net only. Does anyone know what is happening with vb.net going forward? I would hate to get stuck into the vb.net world and have it killed off within a few years. Thanks Tom
RE: vb.net
Didn’t he die at Trafalgar? From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Bill McCarthy Sent: Tuesday, October 13, 2015 1:29 PM To: Nelson; ozDotNet Subject: RE: vb.net Really ? What ‘legacy’ things are you referring to ? From: Nelson Sent: Tuesday, 13 October 2015 12:52 PM To: ozDotNet Subject: Re: vb.net Personally i would turn down such offer - actually wouldnt even be applying in the first place. pretty good market out there with JS and C# .NET, try looking else where if you can if you just recently graduated, your modern mindset would have a hard time dealing with VB and the legacy system. you will likely lose passion just my 2 cents On 13 October 2015 at 12:47, Tom P wrote: Guys I've been offered a junior dev job but they insist on vb.net only. Does anyone know what is happening with vb.net going forward? I would hate to get stuck into the vb.net world and have it killed off within a few years. Thanks Tom
RE: vb.net
Really ? What ‘legacy’ things are you referring to ? From: Nelson Sent: Tuesday, 13 October 2015 12:52 PM To: ozDotNet Subject: Re: vb.net Personally i would turn down such offer - actually wouldnt even be applying in the first place. pretty good market out there with JS and C# .NET, try looking else where if you can if you just recently graduated, your modern mindset would have a hard time dealing with VB and the legacy system. you will likely lose passion just my 2 cents On 13 October 2015 at 12:47, Tom P wrote: Guys I've been offered a junior dev job but they insist on vb.net only. Does anyone know what is happening with vb.net going forward? I would hate to get stuck into the vb.net world and have it killed off within a few years. Thanks Tom
Re: vb.net
Personally i would turn down such offer - actually wouldnt even be applying in the first place. pretty good market out there with JS and C# .NET, try looking else where if you can if you just recently graduated, your modern mindset would have a hard time dealing with VB and the legacy system. you will likely lose passion just my 2 cents On 13 October 2015 at 12:47, Tom P wrote: > Guys I've been offered a junior dev job but they insist on vb.net only. > Does anyone know what is happening with vb.net going forward? I would > hate to get stuck into the vb.net world and have it killed off within a > few years. > > Thanks > Tom >
vb.net
Guys I've been offered a junior dev job but they insist on vb.net only. Does anyone know what is happening with vb.net going forward? I would hate to get stuck into the vb.net world and have it killed off within a few years. Thanks Tom
