Archive: December, 2007
My wife started to make this delicious dish a while ago. It is really good, very simple, and quick to make. This recipe will feed about three people, goes well with rice or noodles, and takes about 30 minutes from start to finish.
- Stir Fry Veggies – Get enough to fill a wok 3/4 full
- 1 tbsp. Cornstarch
- 1/4 Cup Soy Sauce
- 2 tbsp. Vinegar
- 3 tbsp. Brown Sugar
- 1 tsp. Garlic Powder
- Pineapple Chunks – Keep some of the juice (Optional)
- Worcestershire Sauce (Optional)
Begin by cooking the veggies. Depending on how crisp you want them will determine how long to cook them for. Next stir together the cornstarch and soy sauce in a separate cup and then add it to the wok. Add the vinegar, brown sugar, and garlic powder directly to the wok and stir together. If you would like a sweeter or richer flavor, add some pineapple chunks with some juice or Worcestershire sauce. Bring to a boil and serve!
About every other week I will need to know something about the life cycle of an ASP.NET page and for some reason it takes me a while to find it on the Internets. Below I’ve added an ordered list of the events which fire during the life cycle of an ASP.NET Application, Page, and Control. And then as a bonus I’ve included an image which shows most of it courtesy of Leon Andrianarivony. Enjoy!
There is a special list in the registry which you can use to prevent user accounts from appearing on Vista’s welcome screen. To add a user account to this list, open the registry editor (regedit.exe) and navigate to:
If SpecialAccounts or UserList does not exist, create it. Create a DWORD registry value for the name of the user that you want to hide and name it the same as the user. Make sure it is set to 0, which will flag the user as being hidden on the welcome screen. If you set it to 1, then it will be visible.
And that’s it!
Lately I’ve been experiencing some frustrating problems with references to DLL files in a Visual Studio solution. Since I’m working with a team of other programmers, we are obviously using a code versioning system—in this case SourceSafe. It seems that nearly every time I “get the latest version” of the solution from SourceSafe and then try to build it, I will get errors with references to missing DLLs. However, the “missing DLLs” actually exist. The problem is that the references to these DLLs within the solution are wrong.
Because each of the other programmers have a different path to their own copies of the same solution, they also have different paths to the DLLs that are included in that solution. One programmer will notice that his stuff isn’t compiling, he’ll fix the reference error, check it in, and then simultaneously break it on all the other programmers’ machines (Or at least all those will a different file structure).
To fix it, you’ll want to use “Reference Paths” within Visual Studio:
- In Solution Explorer, right-click your project node and click Properties. The Project Designer should appear.
- If you are using Visual Basic, select the References page and click the Reference Paths button. In the Reference Paths dialog box, type the path of the folder that contains the DLL that you want to reference in the Folder field, then click the Add Folder button. If you are using C#, select the Reference Paths page. In the Folder field, type the path of the folder that contains the item you want to reference, and then click the Add Folder button.
That’s it! Reference Paths are saved within each user’s own profile, so they will not be propagated to the other SourceSafe users when you check in your files. When you build a solution, Visual Studio will first try to find the DLL with the hardcoded path that is provided within the solution. If it can’t find it, then it will look within the Reference Paths for the file, where you should now have the correct reference to the DLLs.