Initial feedback for appharbor
First of all I have to say that you have really good, simple getting started instructions. I was up and running very quickly.
2 things that I'd like to see improved are:
Deploy link should tell me 'deployed' on my current deployment. It
says deploy like the others. I see the deployed timesstamp; so not
as important but it'd be nice.
Regarding
http://support.appharbor.com/kb/getting-started/managing-environments
-can you support build configurations? Debug/Staging/Release;
Debug/Test/Release; Local/Debug/Release? --something like this for
conditional builds. In particular, I'm interested in http://completedevelopment.blogspot.com/2009/05/blog-post.html
so I can get code coverage. Also supporting MSTest would be
nice.
Discussions are closed to public comments.
If you need help with AppHarbor please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by rune on 15 Jan, 2011 01:37 AM
Hi David,
thanks for your feedback. Good idea to show what build is the currently deployed one. I've updated the list of builds on the application page, so you can now tell which one is currently deployed, as it will read "active" rather than having a "deploy" link.
We would like to support MSTest and we're currently investigating potential licensing issues with Microsoft. Hopefully they'll realize that it's not cool to restrict people from using their testing framework just because it's tied to Visual Studio as-is, but we'll have to see about that. We'll keep you posted (probably on the blog) as soon as this has been settled.
Regarding your suggestion with build configurations - I'm assuming you're referring to the web.config transformations that allows for debug/release environments? It would be great if you could add it as a feature request on http://appharbor.com/feedback - otherwise I'll like do it for you.
It's basically on our roadmap to support varying environment better, but I would like to see how many are actually interested in the transformations feature that is provided by MVC and would love some more input on how to handle it. My personal opinion is that the web.config transformation feature is unnecessarily difficult to use (and based on crude xml configuration), and less relevant as config files can't be changed separately of a new build anyways. This means environment configuration might as well be handled in code.
On the other hand, we definitely want to make it as convenient and easy for people to migrate their applications to our platform, so if this is a major point for you we will prioritize it higher.
Best regards,
Rune
rune closed this discussion on 15 Jan, 2011 01:37 AM.
rune re-opened this discussion on 27 Jan, 2011 06:36 AM
Support Staff 2 Posted by rune on 27 Jan, 2011 06:36 AM
Hi David,
just wanted to let you know that we're now supporting MSTest.
Best regards,
Rune
rune closed this discussion on 27 Jan, 2011 06:37 AM.