Comments for Look alive. Here comes a buzzard. http://blog.glenc.net Treading water in a sea of man-made confusion. Mon, 01 Dec 2008 20:52:35 +0000 http://wordpress.org/?v=2.6 Comment on WSS 3.0 Web Service Quick Reference by Saurabh k. Tripathi http://blog.glenc.net/2006/11/24/wss-30-web-service-quick-reference/#comment-14532 Saurabh k. Tripathi Tue, 25 Nov 2008 04:33:00 +0000 http://blogtmp.glenc.net/2006/11/24/wss-30-web-service-quick-reference/#comment-14532 Hi srinivas, put your coad in try catch block(see the code below)...that'll give you exact error. try { user.AddUserToRole(roleName, "saurabh_kunapalli2.mi", "RED001\\saurabh_kunapalli2.micr", "saurabh@kunapalli2.microsoftonline.com", "Some Notes"); txt_AddUserToRole.Text = "user added successfully"; } catch(System.Web.Services.Protocols.SoapException ex) { txt_AddUserToRole.Text = ex.Detail.OuterXml; } Hi srinivas,
put your coad in try catch block(see the code below)…that’ll give you exact error.
try
{
user.AddUserToRole(roleName, “saurabh_kunapalli2.mi”, “RED001\\saurabh_kunapalli2.micr”, “saurabh@kunapalli2.microsoftonline.com”, “Some Notes”);
txt_AddUserToRole.Text = “user added successfully”;

}
catch(System.Web.Services.Protocols.SoapException ex)
{
txt_AddUserToRole.Text = ex.Detail.OuterXml;
}

]]> Comment on How to use source control - treat it like a video game by João Marcus Christ http://blog.glenc.net/2008/11/15/how-to-use-source-control-treat-it-like-a-video-game/#comment-13633 João Marcus Christ Sun, 16 Nov 2008 13:36:16 +0000 http://blog.glenc.net/?p=108#comment-13633 "The more frequently you commit, and the more organized you are about it, the less you have to worry about keeping track of every change you make." If you're using SVN and only commiting "production-ready" code, it's not possible to commit ofter. What, you never heard of companies that don't have any kind of automated testing, test plans, or even test/staging databases and application servers? “The more frequently you commit, and the more organized you are about it, the less you have to worry about keeping track of every change you make.”

If you’re using SVN and only commiting “production-ready” code, it’s not possible to commit ofter. What, you never heard of companies that don’t have any kind of automated testing, test plans, or even test/staging databases and application servers?

]]> Comment on How to use source control - treat it like a video game by Joe the Killjoy http://blog.glenc.net/2008/11/15/how-to-use-source-control-treat-it-like-a-video-game/#comment-13616 Joe the Killjoy Sun, 16 Nov 2008 07:58:25 +0000 http://blog.glenc.net/?p=108#comment-13616 The tricky part is merging the savegames... The tricky part is merging the savegames…

]]> Comment on How to use source control - treat it like a video game by JLR http://blog.glenc.net/2008/11/15/how-to-use-source-control-treat-it-like-a-video-game/#comment-13603 JLR Sun, 16 Nov 2008 07:08:16 +0000 http://blog.glenc.net/?p=108#comment-13603 You know, this actually helps. I already commit often, but somehow thinking about it this way makes things clearer. I think this will help orient me when using version control. Thanks for taking the time to write it up! You know, this actually helps.

I already commit often, but somehow thinking about it this way makes things clearer. I think this will help orient me when using version control.

Thanks for taking the time to write it up!

]]> Comment on How to use source control - treat it like a video game by Shawn http://blog.glenc.net/2008/11/15/how-to-use-source-control-treat-it-like-a-video-game/#comment-13572 Shawn Sun, 16 Nov 2008 00:00:25 +0000 http://blog.glenc.net/?p=108#comment-13572 I agree on commit often but I think "quick-save" is a poor analogy. Commits should be more like checkpoints. Places to return to after you've met a certain condition (fixed a problem, updated code, etcetera) rather than when you think you might break something. There should be a milestone, however small it may be. I agree on commit often but I think “quick-save” is a poor analogy. Commits should be more like checkpoints. Places to return to after you’ve met a certain condition (fixed a problem, updated code, etcetera) rather than when you think you might break something. There should be a milestone, however small it may be.

]]> Comment on How to use source control - treat it like a video game by Marius Gedminas http://blog.glenc.net/2008/11/15/how-to-use-source-control-treat-it-like-a-video-game/#comment-13564 Marius Gedminas Sat, 15 Nov 2008 23:37:36 +0000 http://blog.glenc.net/?p=108#comment-13564 There are games where you can save at any point. That doesn't work well with code: you should only be checking in working code. Perhaps a game that has specific save points and won't let you save at other times would be a better analogy. On the other hand, that might leave you checking in not as often as you should be. I prefer to look at source control as a game in its own: find the smallest self-contained meaningful code change on the way to whatever you're trying to achieve, then commit that. There are games where you can save at any point. That doesn’t work well with code: you should only be checking in working code. Perhaps a game that has specific save points and won’t let you save at other times would be a better analogy. On the other hand, that might leave you checking in not as often as you should be.

I prefer to look at source control as a game in its own: find the smallest self-contained meaningful code change on the way to whatever you’re trying to achieve, then commit that.

]]> Comment on How to use source control - treat it like a video game by Successful Scrum | csixty4 http://blog.glenc.net/2008/11/15/how-to-use-source-control-treat-it-like-a-video-game/#comment-13547 Successful Scrum | csixty4 Sat, 15 Nov 2008 20:42:33 +0000 http://blog.glenc.net/?p=108#comment-13547 [...] I talk about the need to treat the less fun aspects of programming like rituals.  For example, treat checking code into source control like saving in a video game: Now, back to my game, what if I come to a fork in the road.  I can go left through the ominous [...] [...] I talk about the need to treat the less fun aspects of programming like rituals.  For example, treat checking code into source control like saving in a video game: Now, back to my game, what if I come to a fork in the road.  I can go left through the ominous [...]

]]> Comment on How to use source control - treat it like a video game by Justin Lilly http://blog.glenc.net/2008/11/15/how-to-use-source-control-treat-it-like-a-video-game/#comment-13544 Justin Lilly Sat, 15 Nov 2008 19:28:31 +0000 http://blog.glenc.net/?p=108#comment-13544 I really like the point you've made here. Haven't really thought of branching in that way. I can't help but be reminded of playing through mike tyson's punchout on my NES emulator. I would save game state after every successful punch so I could quickly revert if something went wrong. A bit of cheating, but a fond memory :) I really like the point you’ve made here. Haven’t really thought of branching in that way.

I can’t help but be reminded of playing through mike tyson’s punchout on my NES emulator. I would save game state after every successful punch so I could quickly revert if something went wrong. A bit of cheating, but a fond memory :)

]]> Comment on How to use source control - treat it like a video game by Nub http://blog.glenc.net/2008/11/15/how-to-use-source-control-treat-it-like-a-video-game/#comment-13534 Nub Sat, 15 Nov 2008 18:14:43 +0000 http://blog.glenc.net/?p=108#comment-13534 Am I the only one who, upon reading the title, thought this would be something about highscores in terms of number of commits? Good article, I absolutely agree. I used to do the same thing on "Below the Root" back on the Apple IIc -- omg I am old. Am I the only one who, upon reading the title, thought this would be something about highscores in terms of number of commits?

Good article, I absolutely agree. I used to do the same thing on “Below the Root” back on the Apple IIc — omg I am old.

]]> Comment on WSS 3.0 Web Service Quick Reference by srinivas reddy http://blog.glenc.net/2006/11/24/wss-30-web-service-quick-reference/#comment-12713 srinivas reddy Thu, 06 Nov 2008 12:11:42 +0000 http://blogtmp.glenc.net/2006/11/24/wss-30-web-service-quick-reference/#comment-12713 iam trying to add a user to a list using addRoleToUser() method in usergroup.asmx. group.AddUserToRole(roleName, "Amarnath", vertex\srinivas.t, "", userNotes); Here iam getting the Soap Server Exception. Guide me in this issue. iam trying to add a user to a list using addRoleToUser() method in usergroup.asmx.
group.AddUserToRole(roleName, “Amarnath”, vertex\srinivas.t, “”, userNotes);

Here iam getting the Soap Server Exception. Guide me in this issue.

]]>