Visual Studio and therefore C# on iphone/os x only makes sense in the context of developing for Silverlight. Silverlight already runs on OS X. Silverlight does not run on iPhone OS. But there are still options for doing C# with both iPhone and OS X, just not with Visual StudioNo way in hell VS itself gets fully ported to Silverlight any time soon, so VS on OS X is not going to be an option. If you want to write Silverlight to target a Mac, you either use Visual Studio on Windows and deploy the Silverlight app to OS X, or you can use Eclipse on a Mac.Silverlight doesn't run on iPhone OS (though it would be awesome if it did - I still don't see it happening). If you want to develop with C# for iPhone, closest you get is with MonoTouch, which gives you MonoDevelop as the IDE, and thus C# on a Mac[Edited on May 28, 2010 at 11:38 AM. Reason : SL = silveright vs SL = Snow Leopard confusion]
5/28/2010 11:25:52 AM
I was at the Launch 2010 conference today in Raleigh ...Getting to see a live Windows Phone 7 device and a demo of developing for it was pretty great.But ... the remainder of the conference was barely worth my time. I would have learned more from an online tutorial or a video because they ran through things too fast to be absorbed and they didn't take very many questions. It was like a quick show and tell. However, I did learn about things I never would have checked into on my own.I'm posting it here because they were using Visual Studio 2010 throughout and I was impressed with what I saw. One big issue is that they all configured their screens for the projector and VS looks like crap when squeezed onto a projector's resolution.Oh and if anyone was wondering, they didn't pass out software, just stickers and pads of paper
6/2/2010 9:54:26 PM
not trolling at all, but it just shows how clueless I am when it comes to this stuff... it blows my mind that what he has shown took one person's full time (40+ hours a week) for two years
6/2/2010 10:05:37 PM
I also went to the launch event and left after they finished with the Phone stuff. I thought about staying, but my laptop battery was about to die and I couldn't convince myself that the presentations would be any more relevant to my work from that point on.
6/2/2010 11:43:06 PM
6/3/2010 12:29:39 AM
I was also at the event today. Everything shown today I had seen or done before so it was a tad boring, but I drank my weight in free coffee and did win one of the Mice at the end though so it wasn't a total waste.I wish they wouldn't bother writing/manipulating code at all. Just say what you are doing, show the code for a bit (use snippets for any any/all alterations) and simply show the results. SO much time is wasted doing trivial stuff (like during a bit where he's supposed to be showing off Windows 7 tie-ins he spends time manually creating a WCF data service and hooking into it)I've moved to VS2010 at work awhile back and love it. Only drawback is the delay in Windows Mobile SDK and the fact that only the latest mobile products (WP7) will be supported so my surveying projects in WM5 will keep VS2008 around.
6/3/2010 12:41:29 AM
http://www.engadget.com/2010/06/03/ballmer-silverlight-certainly-doesnt-run-on-the-iphone/
6/3/2010 2:27:56 PM
^wrong thread i think. There is a microsoft thread. This is the Noen works for Microsoft thread
6/3/2010 2:31:29 PM
in the context of "Will there be a suprise silverlight on iphone announcement at wwdc?" i think its a valid post.
6/3/2010 2:38:00 PM
Was in this thread, started when I posted
6/3/2010 2:39:04 PM
6/3/2010 4:30:51 PM
k then what about vs2010 otherwise supporting iphone app development?
6/3/2010 4:51:12 PM
It will not support native iPhone application development. Third parties may develop solutions (none I am aware of), but it definitely isn't going to be a Microsoft supported environment. It's not even possible for us to do, because Apple has locked Objective C to OSX only.
6/3/2010 5:12:58 PM
suxoh well, I can't wait until we switch to 2010 at work.
6/4/2010 12:49:46 PM
I am still loving VS2010. A lot of the nitpicky annoying things from 2008 and before seem to have been handled!The only feedback I would have right now is around intellisense. For some reason enum intellisense seems broken.If i have an enum and declare a variable of that enum type, and go to assign it a value, i dont get intellisense.I type:Dim _SomeValue As eMyEnum_SomeValue =And I dont get the available enum values like I did in 2008, I get the full intellisense listing of every available object, not just the ones that make sense.The other wierd intellisense issue that I am running into is editing XAML in VS. If i go to set a property to something in a resource library, like the background color of a ui element, I dont get intellisense for what is available. The background compiler is fast enough that i do get the squiggly "idiot lines" if I mistype the resource key, but it would be nice to not have to open my libraries and find the exact spelling of the one I am looking for.I type this:Background="{DynamicResource And dont get a list of anything. 2010 is my first serious foray into using WPF for a production utility, so I am not certain if this has ever shown intellisense (unlike my first issue). It seems like it should show a list of the available Application Resources though.
6/24/2010 9:49:24 PM
[Edited on July 2, 2010 at 3:46 PM. Reason : https://connect.microsoft.com/VisualStudio/feedback/details/532806/]
7/2/2010 3:44:55 PM
^You have some custom extension installed (The "hg" context menu items) that are making the context menu overflow the monitor size you have. Blame that on the 3rd party tool, not on VS.
7/2/2010 5:28:30 PM
with that much real estate you'd think vs / windows would put the context menu a little higher than halfway down the screen...[Edited on July 2, 2010 at 6:18 PM. Reason : ]
7/2/2010 6:18:04 PM
^^ no way dude. that is the default behavior of VS2010 out of the box.[Edited on July 2, 2010 at 6:52 PM. Reason : check the comments on the Connect ticket]
7/2/2010 6:51:57 PM
So when people talk about C# on OS X I guess the Mono runtime doesn't count.
7/2/2010 7:31:48 PM
http://blogs.msdn.com/b/visualstudio/archive/2010/10/14/hotfixes-available-for-scrolling-context-menu-problem.aspxfinally, a fix for ^^^^^
10/14/2010 9:57:47 PM
So in layman's terms and in a quick brief - who would use this software and for what purpose? It seems interesting enough to read through this thread about it but half this stuff is way over my head and I'm still not sure what the definitions mean even browsing through wiki and the like as they just reference more acronyms and software I have no knowledge about.I know it's a somewhat common Microsoft product but it's something I've had on my work comp and never needed to use and probably won't ever need to.[Edited on October 14, 2010 at 11:47 PM. Reason : .]
10/14/2010 11:44:53 PM
Visual studio is an IDE, integrated development environment for Windows applications. Basically you use it to write programs.
10/14/2010 11:46:31 PM
but if you're one of the kewl kidz you'll use gcc to make programs that also run on Linux and the Mac and other platforms; I'm a fan of the Code::Blocks frontend because it also makes use of the wxWidgets cross-platform toolkit and it is also free and open-source
10/15/2010 12:02:34 AM
10/15/2010 12:55:51 AM
10/15/2010 3:54:32 AM
I can't wait until we switch to 2010 at work.
10/15/2010 11:24:10 AM