I have no affiliation with AppHarbor, but I do know a lot about Azure. I don't think it's really the best choice for running a platform like this, so I doubt they are using it. It's more of a greenfield platform because while you certainly can run legacy apps on it, in order to fully take advantage of the platform you have to design for it. For example. SQL Azure is a subset of what SQL Server 2008 R2 offers, so while if you use something like NHibernate, your app's data access code may still work, you may find that you have a reporting query that uses a specialized T-SQL feature it doesn't work.
Our goal is to make people c# developers use the cloud. I do agree that a lot of c# developers doesn't use the cloud yet, but I don't see how that should keep Appharbor from becoming popular.
A more likely cause for the lack of cloud-hosted c# apps would probably be, that there aren't really any viable options for c# developers who wants their app hosted in the cloud (Azure isn't really the bee's knees, right?)
I'm currently stuck on a mix of shared hosting and VPS with my asp.net apps. I'm really keen to move to something simpler that also fits with my git-workflow. AppHarbor looks very promising and much simpler than Azure (hopefully cheaper too!)
Azure is expensive, but its getting better. They enabled full IIS in the latest 1.3 release. Now you can host multiple websites within a single WebRole and map subdomains to each site. Remote Desktop access and full admin rights removed many other restrictions as well.
SQL Azure still has the craziest pricing. $10/gb. Thats why we decided to go the 'NoSql' route and use Table Storage for everything possible.
I hope you have a nice roadmap of features planned. Like I mentioned in other comments, our company is completely hosted within Azure and would love to try out your service. But, I imagine that most companies like ours are going to need a lot more sophisticated 'cloud' services beyond IIS and SQL Server.
For example, how will you compete with Table and Blob Storage? Can I instantly turn up/down new nodes? Will you have caching?
We do and for now we'll be focusing on implementing rudimentary support for stuff everyone needs. To compete with Azure's Table/Blob storage I think a combination of S3 and SimpleDB (or an rdbms) would be the best option... Obviously we would like to make it as easy for people to get started with this as possible, so we'll probably end up wrapping it in some way convenient to our users - for now people should feel free to use these services directly from amazon.
The ability to instantly scale up/down is a feature at the core of our business and it will be available no later than our official launch.
Providing various caching options is also ranked highly on our feature list and will be available as an add-on (and paid) service.
I can imagine this being popular in the enterprise, especially if it supports other version control systems like subversion. I know many enterprise shops are researching cloud hosting for Java and .NET apps.
msysgit works just fine, both 32/64bit windows...however, I agree I'm not aware of many windows devs that use it. I tend to straddle win/*nix so I have git/svn installed in both environments for convenience.
I do. The new ASP.NET MVC stuff is really nice, and I suppose the biggest draw for me is that I already use C#/F# on a daily basis, so using ASP.NET is just a matter of learning the API.
If your only experience with ASP.NET was with the old, ASP.NET Forms-based stuff, I understand where you're coming from -- my first development job was writing ASP.NET Forms apps on .NET 1.1...it wasn't pretty, to say the least -- but you should really give the new ASP.NET MVC 2 (or 3, which is almost RTM) a look.
I happen to like writing web apps using .NET. I came across AppHarbor yesterday, got a beta invite and started playing with it today. Yes it's very early, but I thought there might be people here who would find it interesting still.
If you're going to submit your own app, here are some tips:
1) Link your homepage. HN allows you to title your submission and we'll forgive a teensy bit of valuable keyword stuffing in your submission if it's descriptive. Your homepage is always a more valuable landing page than a months-old blog post. If your homepage isn't as descriptive as the blog post, change your homepage then submit.
2) Either be at public launch or public beta when you do. Otherwise, you're blowing a chance to capture and on board a huge number of technically savvy people who will help you find bugs and UX issues in real time. (This was exceptionally helpful to us with Dawdle.com back when.)
3) Please make sure your blog has a big honking link to your homepage, not the blog homepage. Make that link an image with lots of tasty descriptive text to goose your SEO to your homepage, which will undoubtedly serve as your main landing page for normals who are Googling and press who wants to link to you.
It's not my app. I'm just came across AppHarbor yesterday and have been playing with it. The home page is very bare, so I linked to the blog to provide quicker access to info. I guess the guys have been too busy to get the home page ready yet.
I'm sorry if I've damaged the marketing opportunities. I was just excited to see them handing out beta invites and wanted to spread the word :)
