What's holding up .NET 4.5 support on AppHarbor?

http://blog.appharbor.com/2012/08/20/what-s-holding-up-net-4-5-support-on-appharbor

by dmalenko • 14 years ago

26 7 14 years ago

blog.appharbor.com

charliesome• 14 years ago

That's one of the more ridiculous bugs I've heard of...

I wonder what the root cause is.

eckyptang2• 14 years ago

As a frequent user of the .Net stack, this sort of thing is common and very annoying indeed.

I'd guess that it's probably using a temp path which is close to the length of the path limit on Windows and is either not handling it or truncating it. Either that or it's just shoddy code.

elarkin• 14 years ago

You can generally get around windows' 255 absolute character length limits by using UNC paths. We had that problem at my last company, where the system would allow you to write files into a path but not delete them.

There isn't a modern reason for the limit either. NTFS supports longer path names, as does FAT if I remember correctly. Rather irritating.

vyrotek• 14 years ago

Dang, that's too bad. This could have been a great opportunity for them. A lot of people are going stir crazy because Azure doesn't support .Net 4.5 either yet. I imagine a lot of folks (including myself) quickly checked to see if App Harbor supported it.

friism• 14 years ago

Rest assured, we'll have it ready very soon - Microsoft bugs notwithstanding.

phredaustin• 14 years ago

BTW, if you're one of the people waiting for .Net 4.5 on Azure, upvote it here to get Microsoft's focus on it: http://www.mygreatwindowsazureidea.com/forums/34192-windows-...

What's holding up .NET 4.5 support on AppHarbor?

Related Stories