About versioning....
When it comes to version control systems, we developers ask the very same question: Which system must we use?
The default, and probably the most common is the Microsoft's solution, which is SourceSafe.
However, not much has happened with SourceSafe since the current version was released almost 5 years ago, and I still have a lot of points to complain about this version, like why dont we have a sourcesafe.net? Why dont they develop more features or at least fix the weak points?
Myself, I see a lot of reasons to look after for something better than SourceSafe: It is slow, and not mentioning using it across a VPN. It does not handle multiple users editing the same file. It has problems with opening and closing ss.ini, especially over a slow network, which cause us to re-config the environment in our clients constantly. There is no SourceSafe service? and because of this, when a problem happend we have to shutdown and up the server, which personally I find it nasty when you are running SourceSafe on a multi-purpose server machine.
And worst of all: it corrupts the repository every now and then, and Microsft's best practices implore us to run a corruption analyzer every week!
So what are the alternatives: I know the PVCS, when I used to work with Delphi, which works great over the Internet, but...hey, is Borland, and even thou we like their professionals, we never know until when they are going to be there releasing new products, and I used to have just pass my mouse over the PVCS option in the menu...it just take forever to release it back to my desktop. There are a couple of SCCAPI implementations for CVS. I heard about Igloo, never used it, thou . There is a modern replacement for CVS as well, but naturally this one is even less compatible with VS.NET.
There also Borland's StarTeam and Rational/IBM's ClearCase, neither of which I know anything about. There is also a new product called SourceGear's Vault, appealing because it runs on .NET.
I saw Draco .NET, but unfortunately it only seems to support SourceSafe and CVS at this stage. I could of course go for CruiseControl, at the expense of NAnt support, which also supports CVS, SourceSafe, ClearCase, PVCS and StarTeam, but I haven�t used it much for professional work.
So...if anyone reads this message and have any good recommendation, please feel free to let me know
www.superedge.com
-E
chapter 2367 of the anti-mac war
www.yaromat.com/macos
That�s pretty cool :-) hahaha !!!
and one of my favorites
http://www.geocities.com/siliconvalley/sector/9295/images/flame-mac/mac-load2.gif :-)
-E
Consider this below
Microsoft strongly recommends that developers find alternatives to Automation of Office if they need to develop server-side solutions. Because of the limitations to Office's design, changes to Office configuration are not enough to resolve all issues. Microsoft recommends a number of alternatives that do not require Office to be installed server-side, and that can perform most common tasks more efficiently and quickly than Automation. Before involving Office as a server-side component in your project, consider alternatives.
Considerations for Server-Side Automation of Office
Now...I had to do this...was requested as part of the parameters, and worst...about 150 users were waiting for a better solution to make them able to keep up a good pace into the system.
There were around 4 nights and tons of caffeinne, but finally I figured it out. The component was done and was rocking, baby!!!
But then I saw this, interestingly in the very last night...
Creating and manipulating MS Office objects within/usign visual studio .net
Office automation link
That�s kinda sucks!!! (just like tonight...Mengo lost to Cruzeiro...sucks...)
I've spend a quite reasonable amount of time trying to figure out a way to bypass the limitations of the office automation model...and now that I've been through the whole thing, I just realized the new version of VS.NET has it all.
anyway... the knowledge and the thinking I spent there was worthed, anyway..
lesson learned :-)
-E
Comprehending IT
Comprehending IT - Take One
Two IT guys were walking across the park when one said, "Where did you get such a great bike?" The second IT guy replied, "Well, I was walking along yesterday minding my own business when a beautiful woman rode up on this bike. She threw the bike to the ground, took off all her clothes and said, "Take what you want."
The second IT guy nodded approvingly, "Good choice; the clothes probably wouldn't have fit."
Comprehending IT - Take Two
An architect, an artist and an IT guy were discussing whether it was better to spend time with the wife or a mistress.
The architect said he enjoyed time with his wife, building a solid foundation for an enduring relationship. The artist said he enjoyed time with his mistress, because of the passion and mystery he found there.
The IT guy said, "I like both."
"Both?"
The IT guy replied "Yeah. If you have a wife and a mistress, they will each assume you are spending time with the other woman, and you can go to the office and get some work done."
Comprehending IT - Take Three
To the optimist, the glass is half full.
To the pessimist, the glass is half empty.
To the IT guy, the glass is twice as big as it needs to be.
Comprehending IT - Take Four
An IT guy was crossing a road one day when a frog called out to him and said, "If you kiss me, I'll turn into a beautiful princess".
He bent over, picked up the frog and put it in his pocket. The frog spoke up again and said, "If you kiss me and turn me back into a beautiful princess, I will stay with you for one week."
The IT guy took the frog out of his pocket, smiled at it and returned it to the pocket. The frog then cried out, "If you kiss me and turn me back into a princess, I'll stay with you for a week and do ANYTHING you want."
Again the IT guy took the frog out, smiled at it and put it back into his pocket. Finally, the frog asked, "What is the matter? I've told you I'm a beautiful princess, that I'll stay with you for a week and do anything you want. Why won't you kiss me?"
The IT guy said, "Look I work in IT. I don't have time for a girlfriend, but a talking frog - now that's cool."
-E
Real Programmers
Real Programmers don't write specs
users should consider themselves lucky to get any programs at all and take what they get.
Real Programmers don't comment their code
If it was hard to write, it should be hard to understand.
Real Programmers don't write application programs
they program right down on the bare metal. Application programming is for feebs who can't do systems programming.
Real Programmers don't eat quiche
In fact, real programmers don't know how to SPELL quiche. They eat snickers and drink coffee.
Real Programmers don't use SAP
SAP is for wimpy application-VBdesign programmers.
Real Programmers' programs never work right the first time
But if you throw them on the machine they can be patched into working in "only a few" 30-hour debugging sessions.
Real Programmers never work 9 to 6
If any real programmers are around at 9 AM, it's because they were up all night.
Real Programmers don't use Visual Basic
Actually, no programmers write in these, after the age of 12.
Real Programmers don't document
Documentation is for simps who can't read the listings or the object deck.
Real programmers think in hexa
no comments.
"Denial is the most predictable of all human responses.
But, rest assured, this will be the sixth time we have destroyed it, and we have become exceedingly efficient at it."
:-) Despite of what others might say or have said..dont't miss it for nothing in this world!!
www.whatisthematrix.com
go see it!!! NOW!!!
-E
HAHAHAH!!! Amazingly funny :-) !
Clippy todo list...Get references from Gates, Balmer, Mom... :-)
gotta check it out
http://www.microsoft.com/office/clippy/
-E
