July 2005 - Posts
Start --> Run then type in the folder name, you are there. I live in LogFiles..now, I simply go Start --> Run --> LogFiles and I am there.
Yup, non admin users cannot do a ping from .net. A non admin user cannot create Raw Sockets. To do this with a non admin user you have to do the following:
add the following registry key: AllowUserRawAccess
Value Type: REG_DWORD-Boolean
Valid Range: 0, 1 (False, True)
Default: 0 (False)
Description: This parameter controls access to raw sockets. If true, non administrative users have access to raw sockets. By default, only administrators have access to raw sockets.
WSUS kicked my butt for the last 48 hours.
Our .NET Windows No Touch Deployment application was up and running at a client site with no problems. The client installed WSUS on the web server last week.
Since this install our app has not run. After hours on the phone with Microsoft and Googling til my fingers bled, I installed everything on another server that did not have WSUS. Everything worked.
I finally got an answer from another contact at Microsoft. It seems SUS should be on a dedicated system and is not recommended on any server that has other roles. This is due to the lockdown of that system when SUS is installed.
So do not install WSUS on your production web server, period. MS suggests a dedicated box or creating a virtual server if you must run it on the same box as IIS.
Numbers and Logistics:
The next public Advanced Master class is on October 17-21st in Washington DC, with Brian Noyes as the instructor. The price is $2,650, and payment should be made in advance to reserve the seat at the class. There is a $350 early-bird discount (till September 1st) for user group members. The venue can seat a limited number - if you are interested, it is better to reserve your place now. To lower the overhead and the class price, we did not set up a registration site, so payment with checks is required. In addition, paying with a PO is just fine (as long as payment is made on receipt of invoice). If you want to sign up, we will send you an invoice made up to your company. To further cut down cost, you will have to bring your own hardware. You will also have to arrange your own travel. You will get detailed logistics help sheet once registered, including hotel recommendation. In addition, each student will receive a copy of Programming .NET Components 2nd edition.
About the Class:
The Advanced Master Class is a 5 days hands-on training, and is the world’s best, most intense .NET training.
On top of the frontal presentations, the class teaches .NET using lab exercise and numerous (over 100) conceptual demos and original tools and utilities. Attendees will find the demos useful not only in class but after it. The demos serve as a starting point for new projects, and as a rich reference and samples source.
For the advanced class we recommend at least 6 months of active .NET development experience. After attending either one of the classes, you will be not just a .NET expert, but also a better software engineer. We conducted the class at many companies big and small, including companies such as Philips and Disney. Please click here for student testimonials.
The instructor for the October class is Brian Noyes, one of the best architects and instructors in the industry:
About Brian Noyes
Brian Noyes is a Microsoft MVP and an international speaker, trainer, writer and consultant with IDesign. He speaks at Microsoft TechEd US, Europe, and Malaysia, Visual Studio Connections, SDC Netherlands, DevTeach Montreal, VSLive!, DevEssentials, and other conferences, and is one of the top rated speakers on the INETA Speakers Bureau. He has published numerous articles on .NET development for MSDN Magazine, CoDe Magazine, The Server Side .NET, Visual Studio Magazine, asp.netPRO, .NET Developer's Journal, and other publications. Brian latest book, Data Binding with Windows Forms 2.0, part of the Addison-Wesley .NET Development Series, will hit the shelves in January 2006, followed shortly thereafter by Smart Client Deployment with ClickOnce.
We have been fighting MSDE for the past 24 hours. Our .Net Windows Client typically uses Sql Server that runs on a box inside the LAN. We were trying set up a laptop to run the app locally using MSDE and a local copy of the database.
Well, after jumping through many hoops we finally got down to this:
SQL Server Driver Cannot Initialize SSPI Package
I found this KB:
What do you know, our encryption dll is named Security.dll. The client passes in an encrypted connection string and it gets decrypted by a dll named Security. I renamed this, did a build and guess what, all worked.
We also had to run svrnetcn.exe to enable tcp.
Ian Griffiths was kind enough to point me to a link about how users feel about dialogs in general:
I do not like the word "but". A colleague once said that every you said\I said up to the word "but" in a sentence is ignored once the word "but" comes out. I listened to myself for a few weeks and sure enough, it made sense.
So I started using the word "though". I have paid particular attention to how other folks use the word "but" in my technical readings. I have found in most cases the word "but" can be replaced with the word "though" or removed all together.
Per the dictionary:
- Despite the fact that; although: He still argues, though he knows he's wrong. Even though it was raining, she walked to work.
- Conceding or supposing that; even if: Though they may not succeed, they will still try. See Usage Note at although.
- However; nevertheless: Snow is not predicted; we can expect some rain, though.
- Informal. Used as an intensive: Wouldn't that beat all, though?
and for "but"
- On the contrary: the plan caused not prosperity but ruin.
- Contrary to expectation; yet: She organized her work but accomplished very little. He is tired but happy.
- Usage Problem. Used to indicate an exception: No one but she saw the prowler.
- With the exception that; except that. Often used with that: would have joined the band but he couldn't spare the time; would have resisted but that they lacked courage.
- Informal. Without the result that: It never rains but it pours.
- Informal. That. Often used after a negative: There is no doubt but right will prevail.
- That... not. Used after a negative or question: There never is a tax law presented but someone will oppose it.
- If not; unless: “Ten to one but the police have got them” (Charlotte M. Yonge).
- Informal. Than: They had no sooner arrived but they turned around and left.
- Usage Problem. Except.
- Merely; just; only: hopes that lasted but a moment.
- Used as an intensive: Get out of here but fast!
- Were it not for: except for: We would have reached the summit but for the weather.
Not that I am proposing you change your vocab, "but" give it a listen to see how often you "but".
When I first got started with .NET I was on my own. I worked alone in a shop where nobody else knew .Net. I found the www.develop.com LISTSERVS very helpful, though I found myself posting to them too much.
What do I mean? Well, folks were quick to point out the fact that I was not researching things on my own. For the most part I did do some research, though I must admit I had many knee jerk posts, pretty much saying "help". Looking in the SDK, looking at the generated IL, Googling, picking up a book have all made me a better .NET developer.
I now try to be mindful of everyone's time and do all the work I can before I post. So, if you see a post by me trust me when I say I have nowhere else to turn. I got mad at first when folks told me to research\demo or whatever else it took to figure something out on my own first. 3+ years later though, I am better off because of their advice to do all I could on my own before I post.
I say thanks to those who, sarcastically, told me to stop posting so many questions.
When I see someone else doing this now I try to help them too. Usually, they are mad\pissed off\hurt and the like. I have dropped out of 2 LISTSERVS today because of this. I try to "teach a man to fish.." and too many folks get pissed...all they want is an immediate answer, fix it, move on, get a problem, post, fix it, move on, etc... This is not the way "I work".
Joe was kind enough to refer me to this jpg which sums up my feelings on the topic:
More Posts Next page »