I for one welcome our new BizX over...Oh, who am I kidding? I haven't logged in close to ten years. I'll probably log in again when Slashdot gets sold again to post about the same message. Carry on./waves feebly.
I disagree. Rails is fantastic for quickly rolling database-driven forms apps. It includes some nice helpers for quickly integrating asynchronous behavior (Ajax), but it's certainly not mandatory. PHP5 doesn't include an OR mapper, and nor should it; an OR mapper should be part of a separate framework or library (just as it is with Ruby and Ruby on Rails). I think that Rails actually has a fairly steep learning curve. It has *very* specific ways of handling most things, and trying to fight against these things will only come back to hurt you in the end. Additionally, since it requires you to function in an MVC mode, there might be an additional bit of learning present as you figure out how to properly separate your app into presentation, model and controller layers.
At the end of the day, it all comes down to need and experience. If you know how to use PHP, why not use it? If you have to integrate a new feature into an existing Rails app, then you'd better learn Rails in a hurry. Personally, I'll build Windows server-targeted web apps in ASP.NET because I know the tooling and the backend. If I'm hosting on Linux or UNIX, I'll write it in Rails because the language and frameworks are so much nicer to use than PHP.
I think there are actually a couple different PHP environments out there for Visual Studio. You can find the full list of addins and packages to complement Visual Studio on our VSIP partner catalog.
Thankfully, my Microsoft salary has long since enabled me to replace my Ikea furniture;-) The meatballs are excellent, though, I must say, as are the lingenberries.
Re:One topic I'd like to see covered.
on
Practical Ruby Gems
·
· Score: 2, Interesting
Have you considered using Mongrel instead? It seems to signficantly less wonky than Apache when it comes to running RoR sites.
Quicktime (which is what iTunes uses under the covers) gets VERY grumpy when you try stepping over it in a debugger while Fairplay'd music is loaded. I ran into this while I was working on a new feature for iRooster 3.0, as the first song in my iTunes library happens to be an M4P. I'm sure there are things you could do to circumvent this, but I have no clue what they'd be. (yes, I do work for Microsoft, but I also love writing Mac software in my spare time;-)
What about RapLeaf? Although it's centered around ratings for conducting transations, I have to believe their system would be pretty effective across a broad spectrum of reputation and ratings needs. Plus, they offer a set of APIs, which is always handy.
This is not a criticism of the people on the team because I can't possibly know anything about the people on the team (well, I know that Aaron Brethorst turned his last name into a verb, which is pretty creepy, but we'll let that slide).
lol:) Are you referring to the pattern on my shirt? Also, I should mention that I spend most of my time on Popfly either designing new features, implementing them, or fixing bugs. I may have the word "manager" in my title, but I also have a computer science degree.
Hah, don't think I can today:) We're rapidly approaching a deadline and it's all hands on deck, but thanks for the note! By all means, please let me know if I can offer you any more assistance with VS on Vista. You can reach me at abreth [here's an atmark] microsoft [here's a dot] com.
Sure. Make a shortcut to devenv (or vcsexpress, etc. if you're using an express product). Right-click on it, choose Properties, choose the Shortcut tab, click the Advanced button, check "Run as administrator". That should do it for you.
I actually wrote that message:) We officially recommend that you always run VS 2005 with elevated privileges. I personally (i.e. not speaking as an official spokesperson for Microsoft) believe that most scenarios work just fine without admin privileges. We could have forced VS 2005 to launch with elevated privileges on Vista.
Yes, I readily agree that debugging against Cassini (the web server included with VS 2005) is wonky when you're not running Visual Studio as an administrator. Try Winforms development and debugging; you won't experience these issues. Whether or not you need to launch VS as an administrator is really dependent on what you use Visual Studio for. YMMV, and all that.
This doesn't actually uninstall the application, however. Most applications use NSUserDefaults, at the very least, which stores a dictionary in ~/Library somewhere (and possibly/Library). You need to delete this, if you want a complete uninstall.
And even this doesn't necessarily clean all the goop off your system when you delete an application. A lot of apps (including one that I do in my spare time) will also write files to ~/Library/Application Support, and potentially other folders. Firefox does this, as does Camino. That said, I'm still a huge fan of how you install most apps on OS X; I think that the drag and drop installation mechanism is very clean, and incredibly nice.
Just to clarify, x86 Vista (but not 64-bit Vista) will virtualize writes to HKLM, HKCR, the Windows directory, Program Files, and a few other locations under the following circumstances. If your application does not include a <trustInfo> section in its Fusion manifest (or if it doesn't have a manifest at all) it will be virtualized unless the application is specifically on Vista's do not virtualize list. Visual Studio (or, more accurately, devenv.exe, the Visual Studio shell application) is on the do not virtualize list, for example.
Once your application has a Fusion manifest with a trustInfo section, it will stop being virtualized. This is where your app should end up. You don't want it to be virtualized, since this may lead to serious problems on x64/IA64 versions of Windows.
Yes, you hit the nail on the head: it absolutely would be. VS 2005 RTM'd about 12 months before Vista did, though, and their design for UAC changed in the interim. Even if we'd done that work-which is decidedly not trivial-it's entirely possible that the behavior that worked for us in the Vista Beta 1/Beta 2 timeframe wouldn't have worked quite right at RTM.
What's tricky is that administrative privileges are assigned on a per-process basis when the process starts up. The net result of that is that we'd have to factor all of these pieces of code throughout the product into separate executables, and then ShellExecute() them.
VS2005 does not require you to run with admin privileges. There are some scenarios that require this, but they're generally the exception rather than the rule. If you want to do something like create a new IIS website on your local machine from within VS you'll need to launch VS elevated, but this is because IIS requires administrative privileges to accomplish this task. For VS 2005, there wasn't much we could do about that. Let me know if you want more information about the topic. I was the developer division's go-to guy for UAC for a year.
Slashdot Mirror
I for one welcome our new BizX over...Oh, who am I kidding? I haven't logged in close to ten years. I'll probably log in again when Slashdot gets sold again to post about the same message. Carry on. /waves feebly.
I disagree. Rails is fantastic for quickly rolling database-driven forms apps. It includes some nice helpers for quickly integrating asynchronous behavior (Ajax), but it's certainly not mandatory. PHP5 doesn't include an OR mapper, and nor should it; an OR mapper should be part of a separate framework or library (just as it is with Ruby and Ruby on Rails). I think that Rails actually has a fairly steep learning curve. It has *very* specific ways of handling most things, and trying to fight against these things will only come back to hurt you in the end. Additionally, since it requires you to function in an MVC mode, there might be an additional bit of learning present as you figure out how to properly separate your app into presentation, model and controller layers.
At the end of the day, it all comes down to need and experience. If you know how to use PHP, why not use it? If you have to integrate a new feature into an existing Rails app, then you'd better learn Rails in a hurry. Personally, I'll build Windows server-targeted web apps in ASP.NET because I know the tooling and the backend. If I'm hosting on Linux or UNIX, I'll write it in Rails because the language and frameworks are so much nicer to use than PHP.
just did, thanks for the suggestion! :)
I think there are actually a couple different PHP environments out there for Visual Studio. You can find the full list of addins and packages to complement Visual Studio on our VSIP partner catalog.
IIS 7.0 uses text file-based configuration.
Thanks for the correction. My Swedish and Norwegian ancestors are-no doubt-spinning in their graves right now.
Thankfully, my Microsoft salary has long since enabled me to replace my Ikea furniture ;-) The meatballs are excellent, though, I must say, as are the lingenberries.
Have you considered using Mongrel instead? It seems to signficantly less wonky than Apache when it comes to running RoR sites.
Couldn't say, to be honest. I know next to nothing about programming devices. Cheers :)
Quicktime (which is what iTunes uses under the covers) gets VERY grumpy when you try stepping over it in a debugger while Fairplay'd music is loaded. I ran into this while I was working on a new feature for iRooster 3.0, as the first song in my iTunes library happens to be an M4P. I'm sure there are things you could do to circumvent this, but I have no clue what they'd be. (yes, I do work for Microsoft, but I also love writing Mac software in my spare time ;-)
What about RapLeaf? Although it's centered around ratings for conducting transations, I have to believe their system would be pretty effective across a broad spectrum of reputation and ratings needs. Plus, they offer a set of APIs, which is always handy.
brethorst.com was taken :)
Cheers,
Aaron
I'm not the project lead. That would be John Montgomery.
Cheers,
Aaron
(the guy on top of the pyramid)
You mean these guidelines?. They pretty easy to find; searching for "Vista Ux Guidelines" will do the trick for you.
Hah, don't think I can today :) We're rapidly approaching a deadline and it's all hands on deck, but thanks for the note! By all means, please let me know if I can offer you any more assistance with VS on Vista. You can reach me at abreth [here's an atmark] microsoft [here's a dot] com.
Sure. Make a shortcut to devenv (or vcsexpress, etc. if you're using an express product). Right-click on it, choose Properties, choose the Shortcut tab, click the Advanced button, check "Run as administrator". That should do it for you.
Cheers,
Aaron
I actually wrote that message :) We officially recommend that you always run VS 2005 with elevated privileges. I personally (i.e. not speaking as an official spokesperson for Microsoft) believe that most scenarios work just fine without admin privileges. We could have forced VS 2005 to launch with elevated privileges on Vista.
Yes, I readily agree that debugging against Cassini (the web server included with VS 2005) is wonky when you're not running Visual Studio as an administrator. Try Winforms development and debugging; you won't experience these issues. Whether or not you need to launch VS as an administrator is really dependent on what you use Visual Studio for. YMMV, and all that.
And even this doesn't necessarily clean all the goop off your system when you delete an application. A lot of apps (including one that I do in my spare time) will also write files to ~/Library/Application Support, and potentially other folders. Firefox does this, as does Camino. That said, I'm still a huge fan of how you install most apps on OS X; I think that the drag and drop installation mechanism is very clean, and incredibly nice.
Just to clarify, x86 Vista (but not 64-bit Vista) will virtualize writes to HKLM, HKCR, the Windows directory, Program Files, and a few other locations under the following circumstances. If your application does not include a <trustInfo> section in its Fusion manifest (or if it doesn't have a manifest at all) it will be virtualized unless the application is specifically on Vista's do not virtualize list. Visual Studio (or, more accurately, devenv.exe, the Visual Studio shell application) is on the do not virtualize list, for example.
Once your application has a Fusion manifest with a trustInfo section, it will stop being virtualized. This is where your app should end up. You don't want it to be virtualized, since this may lead to serious problems on x64/IA64 versions of Windows.
I blogged about this a while back. The first post I made was on virtualization and run levels, and the second one was on creating a UAC-aware manifest file.
We compiled a list of the known issues with running VS 2005 RTM on Vista a while back. There's some interesting stuff in there that explains exactly what happens when you run VS on Vista with standard user privileges. Feel free to let me know if you want clarification on any of the issues raised in that doc.
Cheers,
Aaron
I've been called an astroturfer before. Calling out who I work for helps prevent further such accusations.
Yes, you hit the nail on the head: it absolutely would be. VS 2005 RTM'd about 12 months before Vista did, though, and their design for UAC changed in the interim. Even if we'd done that work-which is decidedly not trivial-it's entirely possible that the behavior that worked for us in the Vista Beta 1/Beta 2 timeframe wouldn't have worked quite right at RTM.
What's tricky is that administrative privileges are assigned on a per-process basis when the process starts up. The net result of that is that we'd have to factor all of these pieces of code throughout the product into separate executables, and then ShellExecute() them.
VS2005 does not require you to run with admin privileges. There are some scenarios that require this, but they're generally the exception rather than the rule. If you want to do something like create a new IIS website on your local machine from within VS you'll need to launch VS elevated, but this is because IIS requires administrative privileges to accomplish this task. For VS 2005, there wasn't much we could do about that. Let me know if you want more information about the topic. I was the developer division's go-to guy for UAC for a year.