|
I think you should try google. If that's not available, try Bing. If that's not available, if I were you, I would SERIOUSLY consider looking for another vocation, like sweeping standing water off sidewalks.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
I recently had a discussion at work about the use of Not... Is or IsNot.
It seems there is no difference between the two, except that IsNot looks more like how you would say something.
For example:
If something IsNot somethingElse Then
End If
However, I prefer Not... Is because that way you always know if something should be true or Not by looking at the beginning of a line of code, like so:
If Not something Is somethingElse AndAlso
something2 Is somethingElse2 AndAlso
Not something3 Is somethingElse3 Then
End If
That code looks clean, because Not (or not Not) is always at the same spot in the line. If I would use IsNot that just as well might not be the case. So by using Not... Is you always know if a condition must be true or not without having to search for the IsNot in every line of code.
But Not... Is sounds a bit weird if you say it out loud.
Does it make any difference 'under the hood' or is it simply a personal preference?
All my colleagues prefer IsNot by the way :p
It's an OO world.
|
|
|
|
|
Personal preferrence. There is no difference between the two "under the hood".
It was put into VB.NET because people were having a hard time reading code that negatated a expression to come up with the real true expression. Basically, the old way it forced people to do this:
Normal layout:
If expression Then
result if True
Else
result if False
End If
'Not' layout:
If expression Then
result if False
Else
result if True
End If
|
|
|
|
|
Thanks for the answer. That is really all I wanted to know 
It's an OO world.
|
|
|
|
|
According to the MSDN:
The IsNot operator cannot be used to compare expressions returned from the TypeOf operator. Instead, you must use the Not and Is operators.
So there must be some difference somewhere.
|
|
|
|
|
Hmm...didn't know that. I just about never compare to a type anyway. It's almost always "Is Nothing".
|
|
|
|
|
If you switch to C#, it becomes a non-issue, or in VB parlance, Not issue (which looks kinda stupid).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
! you = right... Oh wait, you = right!
It's an OO world.
|
|
|
|
|
Hi all,
Can you tell me how to get the msn status by programming, any program language is ok, such as c/c++/java or asp/asp.net/php etc.
What I want is: enter a msn address, such as 'test@hotmail.com', and then the program can return the current status of that account(just online or offline is ok).
Thanks in advance.
hello!
|
|
|
|
|
Answered in the C++ forum. Please post your query in one forum only.
The best things in life are not things.
|
|
|
|
|
can any one tell me about the ideas to reduce the website responce time on production server as my website is taking too long time e.g. 15-20 sec (on staging server its just 2-3 sec).
thanks
|
|
|
|
|
|
Well obviously something is different or even wrong in terms of the environment.
This would include of course something like that the production server has 2 million customer accounts and the staging server only has 2.
But there are many other possibilities.
|
|
|
|
|
|
As an IDE I simply use UltraEdit (a decent text editor).
Then to compile, we have the Nant build scripts (that call csc) and to run tests, NUnit.
To debug, I used to use the ClrDebug and attach to the process. But after installing a new SQL Server sometime last winter it tried to put some lite version of Visual Studio on it and it got rid of that, unfortunately.
I'm meeting with this guys next week for a "knowledge transfer" because I will be responsible for maintaining applications written by this person and I just don't get it. Apparently, he doesn't use an IDE to make .net applications.
I didn't get any requirements for the signature
|
|
|
|
|
Yeah, I'd categorize that as a 'WTF'...
If you're programming in a .NET language, and you're doing it in Windows, there's no reason not to use an IDE, whether it's Visual Studio (even the Express versions), SharpDevelop, or whatever...
Probably a guy used to building C++ applications under *nix with Emacs and gcc...
|
|
|
|
|
Cool. Thanks for the response.
I didn't get any requirements for the signature
|
|
|
|
|
Technically what they are doing is quite possible.
However, why do this effort when there is an editor already available.
Maybe they dont have the funding to buy a full edition of Visual Studio. Express editions can always be tried in that case.
Too much of heaven can bring you underground
Heaven can always turn around
Too much of heaven, our life is all hell bound
Heaven, the kill that makes no sound
|
|
|
|
|
Nope, we are paying a ton of money. We have spent millions on this application and they guy is getting paid quite a bit per hour to do custom work for us.
I didn't get any requirements for the signature
modified on Saturday, July 30, 2011 11:50 AM
|
|
|
|
|
Honestly, Nant and NUnit make sense. Large projects do require build scripts.
NANT or MSBuild both could have been used. The vendor has apparentely gone with NANT.
Nunit is also ok because I suppose all the code is being unit tested (or perhaps Test Driven Development) is being used.
I'm not quite clear why CLRDebug is being used though (when Visual Studio could have been used just as well).
Maybe asking the vendor would be the best approach.
Too much of heaven can bring you underground
Heaven can always turn around
Too much of heaven, our life is all hell bound
Heaven, the kill that makes no sound
|
|
|
|
|
Build scripts is one thing, but coding without an IDE, how can one justify that to a client when you are getting paid by the hour?
I didn't get any requirements for the signature
|
|
|
|
|
ToddHileHoffer wrote: Build scripts is one thing, but coding without an IDE, how can one justify that to a client when you are getting paid by the hour?
From that I can only suppose that you think they are less productive than they would be otherwise.
The fact that you like an IDE and are familiar with it and that you would be less productive without it has absolutely nothing to do with the output of someone else.
Not to mention the following.
- You are suggesting that you personally would be at a measurable disadvantage in your approach to the entire craft without it. So for example there is no point now nor in the future that anyone should ever consider hiring you for a position that requires use of a non-windows system.
- You are suggesting that such a disadvantage would be a significance to your total value as a developer. Which can only suggest to me that you don't spend much time on say design/architecture or at least think that you achieve that only via your IDE. It also precludes things like knowledge transfer, documentation, mentoring, etc.
|
|
|
|
|
jschell wrote: Not to mention the following.
- You are suggesting that you personally would be at a measurable disadvantage in your approach to the entire craft without it. So for example there is no point now nor in the future that anyone should ever consider hiring you for a position that requires use of a non-windows system.
- You are suggesting that such a disadvantage would be a significance to your total value as a developer. Which can only suggest to me that you don't spend much time on say design/architecture or at least think that you achieve that only via your IDE. It also precludes things like knowledge transfer, documentation, mentoring, etc.
No, I'm saying it is inefficient to code .net in a text editor. The entire point of using VS is to increase productivity. Anyone who uses a text editor over an IDE is at a disadvantage. You can make a program work without using an IDE, it is just more difficult and time consuming.
I didn't get any requirements for the signature
|
|
|
|
|
ToddHileHoffer wrote: No, I'm saying it is inefficient to code .net in a text editor. The entire point
of using VS is to increase productivity. Anyone who uses a text editor over an
IDE is at a disadvantage. You can make a program work without using an IDE, it
is just more difficult and time consuming.
I understand exactly what you are claiming.
I can claim exactly the opposite - you are in fact less productive. I can explain why as well...because you rely so much on what the IDE does for you that you do not actually understand what your code is doing. Which becomes a problem when something serious in production goes wrong. Thus you might spends days or even weeks tracking down a problem (which is subtracted from your productive time) when those problems do show up.
Now I could be mistaken in that statement. Because I have no evidence. But your statement has none either.
Personally I believe that neither statement is true. To prove it one must first find a way to actually measure productivity. Then find a way to meaningfully compare it including similar projects, knowledge, experience etc. And use a large enough sample set. Then measure it and determine that it significant in terms of the actual work that a developer does during the week (precluding meetings, design, lunch and time spend on fanstasy football.)
|
|
|
|
|
Whilst IDEs do allow developers who have no more than a basic understanding of what they are doing to reach their end goal, very few developers fall into that category (in my experience at least)
It is also true, however, that one can be an efficient developer without reliance on an IDE.
Considering the original post described the fact that they are using build sripts, unit testing and some form of debugger the variable here is physically writing the code.
VS (as the IDE in question) provides the following (off the top of my head) to facilitate the code writing
- intellisense
- snippets
- shortcuts such as 'find references' and 'goto definition'
- refactoring
Intellisense:
without an IDE providing intellisense (and if your text editor provides this it is arguably an IDE) there is a requirement for the developer to know the entire class library with which they are working or to have a reference, such as MSDN, available (and to be able to search it as efficiently) ... if you can do this, bravo sir!
Snippets:
Easily replicated with copy and paste from a file of useful code snippets
Shortcuts:
Most text editors these days are good at text searching, however they wont have awareness of symbols or scope
Refactoring:
Same as with shortcuts, text replacement is normally pretty good in text editors (and macros can enhance it) but you still lack the scoping and contextual awareness
I would say this is down to developer preference. If you are familiar with a text editor and have a good memory of the class libraries you may well be more efficient using that approach than struggling with VS forcing you to do things the microsoft way. I, myself, cut my teeth in visual studio (im choosing to forget my brief forray into delphi) and would struggle without an IDE, not because I lack skill as a developer (at least i hope) but because everything i type would come out as the first 2 letters followed by a space 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
