Re: Is it time to open source Silverlight?
I'll manage it if it does i have references... --- Regards, Scott Barnes http://www.riagenic.com On Fri, Nov 22, 2013 at 5:25 PM, David Burela wrote: > > http://davidburela.wordpress.com/2013/11/22/is-it-time-to-open-source-silverlight/ > > While I was at the MVP summit I started asking around about if it was time > to open source Silverlight. My thoughts were if the technology is now > considered "done" by Microsoft, then there are few reasons why it couldn't > be released to the community to see what they can do with it. > It was a solid technology (which isn't suitable in the modern world of the > public web), but still has a nice niche on desktop. > It could be interesting to see how the community extends it, and perhaps > even put onto other platforms (like moonlight did). > > A basic game engine could be an interesting direction, or using it to > embed within desktop applications. > The point is, rather than let it rot internally at Microsoft, why not let > the community go wild with it before it gets any more stale. > > > http://davidburela.wordpress.com/2013/11/22/is-it-time-to-open-source-silverlight/ > -David Burela > > ___ > ozsilverlight mailing list > ozsilverli...@ozsilverlight.com > http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight > >
[OT] Public SQL Server
Folks, I want to connect to SQL Server Express on my home server from the outside world. My router forwards tcp 1433 to the correct machine. I can see port 1433 visible but closed in Gibson's port scan. Attempts to connect time out. I'm guessing therefore that I've missed some setting inside SQL Server itself to allow outside connections, but I'm stumped. Any advice anyone?! I'm sure I did this years ago, but it's not so easy this time. Thanks Greg K
Re: [OT] Public SQL Server
I forgot to mention this is SQL Server 2008R2. I have "Allow remote connections to this server" checked. I also noticed in the tcpview utility that the SQL Server process is not listening on port 1433 and it never seems to open (but perhaps it doesn't work the way I expect). I also forward port udp 1434 just in case the sql browser needs this, but it makes no difference -- Greg On 23 November 2013 09:21, Greg Keogh wrote: > Folks, I want to connect to SQL Server Express on my home server from the > outside world. > > My router forwards tcp 1433 to the correct machine. I can see port 1433 > visible but closed in Gibson's port scan. Attempts to connect time out. > > I'm guessing therefore that I've missed some setting inside SQL Server > itself to allow outside connections, but I'm stumped. Any advice anyone?! > I'm sure I did this years ago, but it's not so easy this time. > > Thanks > Greg K >
[OT] Public SQL Server [answer found]
It's all to do with dynamic and static ports, something I haven't anyone discuss before. http://technet.microsoft.com/en-us/library/ms177440.aspx I deleted the Dynamic Ports 0 and added TCP Port 1433 in all the IP settings. I don't know if all need to be changed, but I haven't got time to debug it all. I hope this change doesn't have any nasty delayed side effects. Greg
Re: [OT] Public SQL Server
Off the top of my head I recall something about the appropriate protocols being enabled? i.e. SQL Express may only be listening on local native client and not TCP/IP On 23 November 2013 11:50, Greg Keogh wrote: > I forgot to mention this is SQL Server 2008R2. I have "Allow remote > connections to this server" checked. I also noticed in the tcpview utility > that the SQL Server process is not listening on port 1433 and it never > seems to open (but perhaps it doesn't work the way I expect). I > also forward port udp 1434 just in case the sql browser needs this, but it > makes no difference -- Greg > > > On 23 November 2013 09:21, Greg Keogh wrote: > >> Folks, I want to connect to SQL Server Express on my home server from the >> outside world. >> >> My router forwards tcp 1433 to the correct machine. I can see port 1433 >> visible but closed in Gibson's port scan. Attempts to connect time out. >> >> I'm guessing therefore that I've missed some setting inside SQL Server >> itself to allow outside connections, but I'm stumped. Any advice anyone?! >> I'm sure I did this years ago, but it's not so easy this time. >> >> Thanks >> Greg K >> > > -- regards, Preet, Overlooking the Ocean, Auckland
RE: Is it time to open source Silverlight?
Why do you say that it is unsuitable for modern web? From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of David Burela Sent: Friday, November 22, 2013 2:26 AM To: ozSilverlight; ozDotNet Subject: Is it time to open source Silverlight? http://davidburela.wordpress.com/2013/11/22/is-it-time-to-open-source-silverlight/ While I was at the MVP summit I started asking around about if it was time to open source Silverlight. My thoughts were if the technology is now considered "done" by Microsoft, then there are few reasons why it couldn't be released to the community to see what they can do with it. It was a solid technology (which isn't suitable in the modern world of the public web), but still has a nice niche on desktop. It could be interesting to see how the community extends it, and perhaps even put onto other platforms (like moonlight did). A basic game engine could be an interesting direction, or using it to embed within desktop applications. The point is, rather than let it rot internally at Microsoft, why not let the community go wild with it before it gets any more stale. http://davidburela.wordpress.com/2013/11/22/is-it-time-to-open-source-silverlight/ -David Burela
