I Was Incredibly Wrong
-
Soooo, I don't know if any of you remember, but I showed up a couple of weeks back and started a discussion here in which I blasted Microsoft and talked about my refusal to use their products whenever possible. Many of you pointed out how I was missing out by ignoring Visual Studio, which you lauded as a superb IDE. Since then I've found that you are all absolutely right. I was initially hesitant to just give in and switch my IDE because people told me I was wrong. Made me seem kinda wishy-washy. What broke the camel's back for me and made me switch from SharpDevelop to VS was SharpDevelop's inability to find one single file. I was attempting to follow the directions found here but ran into trouble as MSBuild kept returning an error of "Cannot find AxImp.exe". AxImp was precisely where it needed to be for the system to find it, there didn't seem to be anything in the PATH variable to cause the problem and, seeing as I've never worked with this type of thing before, I had no idea what this meant or how to fix it. Some suggested editing the registry, some suggested installing the Windows SDK. What I did instead was install Visual Studio. Building under VS returned no AxImp errors, either because it actually knows how to find the necessary file or because the installation itself installed whatever I needed to get things going. So now I had VS and I couldn't very well go back. I mean, I didn't know if the AxImp error would still pop up if I tried to go back to SD, and I didn't feel it was worth the trouble. I had an IDE that was giving me none of the problems that SD did. No offense if anyone here volunteers their time writing SharpDevelop source code, but it really was slowing me down. Here's a question: If you're writing a program visually, drawing buttons and drop down menus and whatnot, what do you expect a visual IDE to do well? I would expect it to do exactly what common sense says: handle the code in the Designer.cs files and keep track of changes. I lost count of the number of times that SD actually wrote those changes incorrectly. There is an ironic multi-line comment in each and every one of those cs files that says:
/// /// This method is required for Windows Forms designer support. /// Do not change the method contents inside the source code editor. The Forms designer might /// not be able to load this method if it was changed manually. /// -
Soooo, I don't know if any of you remember, but I showed up a couple of weeks back and started a discussion here in which I blasted Microsoft and talked about my refusal to use their products whenever possible. Many of you pointed out how I was missing out by ignoring Visual Studio, which you lauded as a superb IDE. Since then I've found that you are all absolutely right. I was initially hesitant to just give in and switch my IDE because people told me I was wrong. Made me seem kinda wishy-washy. What broke the camel's back for me and made me switch from SharpDevelop to VS was SharpDevelop's inability to find one single file. I was attempting to follow the directions found here but ran into trouble as MSBuild kept returning an error of "Cannot find AxImp.exe". AxImp was precisely where it needed to be for the system to find it, there didn't seem to be anything in the PATH variable to cause the problem and, seeing as I've never worked with this type of thing before, I had no idea what this meant or how to fix it. Some suggested editing the registry, some suggested installing the Windows SDK. What I did instead was install Visual Studio. Building under VS returned no AxImp errors, either because it actually knows how to find the necessary file or because the installation itself installed whatever I needed to get things going. So now I had VS and I couldn't very well go back. I mean, I didn't know if the AxImp error would still pop up if I tried to go back to SD, and I didn't feel it was worth the trouble. I had an IDE that was giving me none of the problems that SD did. No offense if anyone here volunteers their time writing SharpDevelop source code, but it really was slowing me down. Here's a question: If you're writing a program visually, drawing buttons and drop down menus and whatnot, what do you expect a visual IDE to do well? I would expect it to do exactly what common sense says: handle the code in the Designer.cs files and keep track of changes. I lost count of the number of times that SD actually wrote those changes incorrectly. There is an ironic multi-line comment in each and every one of those cs files that says:
/// /// This method is required for Windows Forms designer support. /// Do not change the method contents inside the source code editor. The Forms designer might /// not be able to load this method if it was changed manually. ///SharpDevelop has basically been abandoned, unfortunately. The team stopped working on it around the time Visual Studio Community Edition was released. It still has some good code (the AddIn system is excellent), and I'm using it for some personal projects that may or may not get released. One thing I like about SD is the fact that it has a WiX Dialog Designer built in.
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
-
Soooo, I don't know if any of you remember, but I showed up a couple of weeks back and started a discussion here in which I blasted Microsoft and talked about my refusal to use their products whenever possible. Many of you pointed out how I was missing out by ignoring Visual Studio, which you lauded as a superb IDE. Since then I've found that you are all absolutely right. I was initially hesitant to just give in and switch my IDE because people told me I was wrong. Made me seem kinda wishy-washy. What broke the camel's back for me and made me switch from SharpDevelop to VS was SharpDevelop's inability to find one single file. I was attempting to follow the directions found here but ran into trouble as MSBuild kept returning an error of "Cannot find AxImp.exe". AxImp was precisely where it needed to be for the system to find it, there didn't seem to be anything in the PATH variable to cause the problem and, seeing as I've never worked with this type of thing before, I had no idea what this meant or how to fix it. Some suggested editing the registry, some suggested installing the Windows SDK. What I did instead was install Visual Studio. Building under VS returned no AxImp errors, either because it actually knows how to find the necessary file or because the installation itself installed whatever I needed to get things going. So now I had VS and I couldn't very well go back. I mean, I didn't know if the AxImp error would still pop up if I tried to go back to SD, and I didn't feel it was worth the trouble. I had an IDE that was giving me none of the problems that SD did. No offense if anyone here volunteers their time writing SharpDevelop source code, but it really was slowing me down. Here's a question: If you're writing a program visually, drawing buttons and drop down menus and whatnot, what do you expect a visual IDE to do well? I would expect it to do exactly what common sense says: handle the code in the Designer.cs files and keep track of changes. I lost count of the number of times that SD actually wrote those changes incorrectly. There is an ironic multi-line comment in each and every one of those cs files that says:
/// /// This method is required for Windows Forms designer support. /// Do not change the method contents inside the source code editor. The Forms designer might /// not be able to load this method if it was changed manually. ///The latest anything .NET by Microsoft is not only good, it is excellent! Continuously outdoing itself for 18 years has led to amazing results! :o :D To be fair I think one must thank the competition for putting Microsoft under pressure to excel. But excel it has! I hope it will continue to do so! :D
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
Soooo, I don't know if any of you remember, but I showed up a couple of weeks back and started a discussion here in which I blasted Microsoft and talked about my refusal to use their products whenever possible. Many of you pointed out how I was missing out by ignoring Visual Studio, which you lauded as a superb IDE. Since then I've found that you are all absolutely right. I was initially hesitant to just give in and switch my IDE because people told me I was wrong. Made me seem kinda wishy-washy. What broke the camel's back for me and made me switch from SharpDevelop to VS was SharpDevelop's inability to find one single file. I was attempting to follow the directions found here but ran into trouble as MSBuild kept returning an error of "Cannot find AxImp.exe". AxImp was precisely where it needed to be for the system to find it, there didn't seem to be anything in the PATH variable to cause the problem and, seeing as I've never worked with this type of thing before, I had no idea what this meant or how to fix it. Some suggested editing the registry, some suggested installing the Windows SDK. What I did instead was install Visual Studio. Building under VS returned no AxImp errors, either because it actually knows how to find the necessary file or because the installation itself installed whatever I needed to get things going. So now I had VS and I couldn't very well go back. I mean, I didn't know if the AxImp error would still pop up if I tried to go back to SD, and I didn't feel it was worth the trouble. I had an IDE that was giving me none of the problems that SD did. No offense if anyone here volunteers their time writing SharpDevelop source code, but it really was slowing me down. Here's a question: If you're writing a program visually, drawing buttons and drop down menus and whatnot, what do you expect a visual IDE to do well? I would expect it to do exactly what common sense says: handle the code in the Designer.cs files and keep track of changes. I lost count of the number of times that SD actually wrote those changes incorrectly. There is an ironic multi-line comment in each and every one of those cs files that says:
/// /// This method is required for Windows Forms designer support. /// Do not change the method contents inside the source code editor. The Forms designer might /// not be able to load this method if it was changed manually. ///Kudos for your honesty. :thumbsup: I've been using Visual Studio for 25 years (it was Visual C++ 6.0 back then) and have never looked back. MS' tooling is the primary reason I stuck with them (and since moved to C# in 2003). So much so, that I use Xamarin/C# to build native Android apps, instead of Eclipse or Android Studio and Java. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Soooo, I don't know if any of you remember, but I showed up a couple of weeks back and started a discussion here in which I blasted Microsoft and talked about my refusal to use their products whenever possible. Many of you pointed out how I was missing out by ignoring Visual Studio, which you lauded as a superb IDE. Since then I've found that you are all absolutely right. I was initially hesitant to just give in and switch my IDE because people told me I was wrong. Made me seem kinda wishy-washy. What broke the camel's back for me and made me switch from SharpDevelop to VS was SharpDevelop's inability to find one single file. I was attempting to follow the directions found here but ran into trouble as MSBuild kept returning an error of "Cannot find AxImp.exe". AxImp was precisely where it needed to be for the system to find it, there didn't seem to be anything in the PATH variable to cause the problem and, seeing as I've never worked with this type of thing before, I had no idea what this meant or how to fix it. Some suggested editing the registry, some suggested installing the Windows SDK. What I did instead was install Visual Studio. Building under VS returned no AxImp errors, either because it actually knows how to find the necessary file or because the installation itself installed whatever I needed to get things going. So now I had VS and I couldn't very well go back. I mean, I didn't know if the AxImp error would still pop up if I tried to go back to SD, and I didn't feel it was worth the trouble. I had an IDE that was giving me none of the problems that SD did. No offense if anyone here volunteers their time writing SharpDevelop source code, but it really was slowing me down. Here's a question: If you're writing a program visually, drawing buttons and drop down menus and whatnot, what do you expect a visual IDE to do well? I would expect it to do exactly what common sense says: handle the code in the Designer.cs files and keep track of changes. I lost count of the number of times that SD actually wrote those changes incorrectly. There is an ironic multi-line comment in each and every one of those cs files that says:
/// /// This method is required for Windows Forms designer support. /// Do not change the method contents inside the source code editor. The Forms designer might /// not be able to load this method if it was changed manually. ///I applaud your willingness to take another look at a product that you believed to be inferior. I, too, detest Microsoft - they were the first to sell defective products and charge for fixes, the first to eliminate product manuals, and the first to abandon any semblance of customer support. Since then, many other producers and programmers have adopted their user-hostile business model to everyone's loss. But the Visual Studio IDE has been from the beginning, and remains, one of the best tools available for the job. Since they introduced the Community Edition, and stopped charging an obscene price for the most rudimentary version, there has been no equivalent product for small developers, and I honor them for that. Thanks for giving them a second look; I don't think you'll be disappointed. I don't do much programming anymore, but when I do, VS is the first IDE I open.
Will Rogers never met me.
-
Soooo, I don't know if any of you remember, but I showed up a couple of weeks back and started a discussion here in which I blasted Microsoft and talked about my refusal to use their products whenever possible. Many of you pointed out how I was missing out by ignoring Visual Studio, which you lauded as a superb IDE. Since then I've found that you are all absolutely right. I was initially hesitant to just give in and switch my IDE because people told me I was wrong. Made me seem kinda wishy-washy. What broke the camel's back for me and made me switch from SharpDevelop to VS was SharpDevelop's inability to find one single file. I was attempting to follow the directions found here but ran into trouble as MSBuild kept returning an error of "Cannot find AxImp.exe". AxImp was precisely where it needed to be for the system to find it, there didn't seem to be anything in the PATH variable to cause the problem and, seeing as I've never worked with this type of thing before, I had no idea what this meant or how to fix it. Some suggested editing the registry, some suggested installing the Windows SDK. What I did instead was install Visual Studio. Building under VS returned no AxImp errors, either because it actually knows how to find the necessary file or because the installation itself installed whatever I needed to get things going. So now I had VS and I couldn't very well go back. I mean, I didn't know if the AxImp error would still pop up if I tried to go back to SD, and I didn't feel it was worth the trouble. I had an IDE that was giving me none of the problems that SD did. No offense if anyone here volunteers their time writing SharpDevelop source code, but it really was slowing me down. Here's a question: If you're writing a program visually, drawing buttons and drop down menus and whatnot, what do you expect a visual IDE to do well? I would expect it to do exactly what common sense says: handle the code in the Designer.cs files and keep track of changes. I lost count of the number of times that SD actually wrote those changes incorrectly. There is an ironic multi-line comment in each and every one of those cs files that says:
/// /// This method is required for Windows Forms designer support. /// Do not change the method contents inside the source code editor. The Forms designer might /// not be able to load this method if it was changed manually. ///:thumbsup: Congrats for being open minded … I use C#/VS for about 18 years now in various projects/teams, underway had an opportunity at least 2x times to work with Java/Eclipse/Tomcat stack, and so far my preference goes to C#/VS environment. I guess it depends a lot on the project what to choose. Anyway being open minded and curious helps to make informed choices :-) (if they are possible of course), BR
-
Soooo, I don't know if any of you remember, but I showed up a couple of weeks back and started a discussion here in which I blasted Microsoft and talked about my refusal to use their products whenever possible. Many of you pointed out how I was missing out by ignoring Visual Studio, which you lauded as a superb IDE. Since then I've found that you are all absolutely right. I was initially hesitant to just give in and switch my IDE because people told me I was wrong. Made me seem kinda wishy-washy. What broke the camel's back for me and made me switch from SharpDevelop to VS was SharpDevelop's inability to find one single file. I was attempting to follow the directions found here but ran into trouble as MSBuild kept returning an error of "Cannot find AxImp.exe". AxImp was precisely where it needed to be for the system to find it, there didn't seem to be anything in the PATH variable to cause the problem and, seeing as I've never worked with this type of thing before, I had no idea what this meant or how to fix it. Some suggested editing the registry, some suggested installing the Windows SDK. What I did instead was install Visual Studio. Building under VS returned no AxImp errors, either because it actually knows how to find the necessary file or because the installation itself installed whatever I needed to get things going. So now I had VS and I couldn't very well go back. I mean, I didn't know if the AxImp error would still pop up if I tried to go back to SD, and I didn't feel it was worth the trouble. I had an IDE that was giving me none of the problems that SD did. No offense if anyone here volunteers their time writing SharpDevelop source code, but it really was slowing me down. Here's a question: If you're writing a program visually, drawing buttons and drop down menus and whatnot, what do you expect a visual IDE to do well? I would expect it to do exactly what common sense says: handle the code in the Designer.cs files and keep track of changes. I lost count of the number of times that SD actually wrote those changes incorrectly. There is an ironic multi-line comment in each and every one of those cs files that says:
/// /// This method is required for Windows Forms designer support. /// Do not change the method contents inside the source code editor. The Forms designer might /// not be able to load this method if it was changed manually. ///Visual Studio is an amazing tool, as you are realizing. But if you still want to bitch at MS, feel free to bash the ribbon to high heck! Working with Word, and continually finding the icons disappearing and not where you expect them is frustrating, to say the least. (Just because you don't have the window wide enough.) X| X| X| X| X| X| And for extra emphasis: X| X| X| X| X| X| I could go repeat the emojis many more times, but you've probably gotten the idea. The old menu system was far superior.
-
Soooo, I don't know if any of you remember, but I showed up a couple of weeks back and started a discussion here in which I blasted Microsoft and talked about my refusal to use their products whenever possible. Many of you pointed out how I was missing out by ignoring Visual Studio, which you lauded as a superb IDE. Since then I've found that you are all absolutely right. I was initially hesitant to just give in and switch my IDE because people told me I was wrong. Made me seem kinda wishy-washy. What broke the camel's back for me and made me switch from SharpDevelop to VS was SharpDevelop's inability to find one single file. I was attempting to follow the directions found here but ran into trouble as MSBuild kept returning an error of "Cannot find AxImp.exe". AxImp was precisely where it needed to be for the system to find it, there didn't seem to be anything in the PATH variable to cause the problem and, seeing as I've never worked with this type of thing before, I had no idea what this meant or how to fix it. Some suggested editing the registry, some suggested installing the Windows SDK. What I did instead was install Visual Studio. Building under VS returned no AxImp errors, either because it actually knows how to find the necessary file or because the installation itself installed whatever I needed to get things going. So now I had VS and I couldn't very well go back. I mean, I didn't know if the AxImp error would still pop up if I tried to go back to SD, and I didn't feel it was worth the trouble. I had an IDE that was giving me none of the problems that SD did. No offense if anyone here volunteers their time writing SharpDevelop source code, but it really was slowing me down. Here's a question: If you're writing a program visually, drawing buttons and drop down menus and whatnot, what do you expect a visual IDE to do well? I would expect it to do exactly what common sense says: handle the code in the Designer.cs files and keep track of changes. I lost count of the number of times that SD actually wrote those changes incorrectly. There is an ironic multi-line comment in each and every one of those cs files that says:
/// /// This method is required for Windows Forms designer support. /// Do not change the method contents inside the source code editor. The Forms designer might /// not be able to load this method if it was changed manually. ///I remember when I forced some Java guys to use it for C++ (and I really had to force them!) They were absolutely blown away by Intellisense, compared to the cheap knock-off in Eclipse.
I wanna be a eunuchs developer! Pass me a bread knife!
-
I remember when I forced some Java guys to use it for C++ (and I really had to force them!) They were absolutely blown away by Intellisense, compared to the cheap knock-off in Eclipse.
I wanna be a eunuchs developer! Pass me a bread knife!
I think you eventually realize that there are great Microsoft projects and bad ones. VS is a great one, although it varies (the help system used to be great, now it sucks). A good example of a bad one is Orca, the msi decompiler, which I eventually found out was written by a Microsoft intern. (To be fair, the mess that is the msi internals was probably a lot of the problem.) Orca helped in Wix installer development, but only after beating your head against the desk for a prolonged period.
-
I think you eventually realize that there are great Microsoft projects and bad ones. VS is a great one, although it varies (the help system used to be great, now it sucks). A good example of a bad one is Orca, the msi decompiler, which I eventually found out was written by a Microsoft intern. (To be fair, the mess that is the msi internals was probably a lot of the problem.) Orca helped in Wix installer development, but only after beating your head against the desk for a prolonged period.
Well, the great news is that the guys who've spent the last 13 years "improving" ms office are being transferred to the VS team. So the kind of great "fixes" that have made ms office the pile of cr@p that what it is today will also be implemented in VS, to **ck up everyone's productivity make sure that coders, too, can profit from the way of the future.
I wanna be a eunuchs developer! Pass me a bread knife!