Hello, I'm Jason
I live with my family in the rolling hills of Northeastern Pennsylvania. I'm a web developer by trade, but have broad experience in various business areas. Want to know more about me?
If you plan on keeping your SQL Express data when you deploy an ASP.NET 2.0 application that you add the applicationName attribute to each of your providers under each special ASP.NET configuration section (ie: Membership). If you do not, ASP.NET 2.0 will look to see if the app was run under a different application or not. If it was, it will create a new application entry in the database and none of your users and profiles will be associated.Read More
You can add personalization to your ASP.NET 2.0 website by adding a Profile section to your web.config file. After you setup your properties, you can begin to add, edit, retrieve, and remove these properties from a profile. Most users like to set personalized properties when they first establish account. By default, the
CreateUser control does not include a step to ask for these profile properties. So, you must create your own step. When you get finished adding in your fields, modify the step’s next button
click event. In the subroutine, add the information to the profile. This can be accomplished by using something similar to this:
I posted a question to the ASPAdvice.com forums regarding the limitations of SqlExpress 2005. I already knew that there was no limitation on connections. However, Scott Forsyth was able to provide me with additional info. Here you go directly from the post: The database size limit is 4GB. There is also a memory limit of 1GB of RAM and a limit of 1 CPU. You can install it on machines with more than 1 CPU, but it only utilizes a max of one. There is a tool to manage SQL Express that can be downloaded from http://lab.msdn.microsoft.com/express/sql/.Read More
This morning while listening to the radio I heard a story about a woman receiving an email. The email she received talked about a girl being approached in a parking lot by 2 guys looking to sell perfume. As the story goes, she received some scratch and sniff samples from these men and ended up passing out. While she was out, she was robbed.
This isn’t a true story. In fact, there are many false stories or “urban legends” that are passed around via email. Folks who have not heard these before are likely to forward these legends off to coworkers, family, and friends.
If you are in an environment that receives similar emails, you should make your users aware. There is a website called Snopes.com with a listing of various email hoaxes. Users (or administrators) should delete these emails and not forward them off. The scariest thing about this is that some day a virus can accompany one of these emails!
-- Just some food for thought.Read More
Microsoft is looking for a new PC design…Read More
With Visual Studio 2005 being released hopefully later this year, MSDN will change its subscription levels. The newest option is a fairly expensive one offering a full Visual Studio 2005 Team Suite. The renewal price for this option is $4598 a year. The next tier of options replace MSDN Universal. Users with MSDN Universal subscriptions will be able to upgrade to Visual Studio 2005 Team Edition for Software Architects, Visual Studio 2005 Team Edition for Software Developers, or Visual Studio 2005 Team Edition for Testers. The renewal price for each of these options is the same as the current MSDN Universal price of $2299. Microsoft will also keep the Visual Studio Professional, MSDN Operating Systems, and MSDN Library Only Subscriptions.Read More
The other Code Camp presentations have been posted on the PhillyDotNet.org website at http://www.phillydotnet.org/LinkClick.aspx?link=378&mid=1031. If you are attending the MSDN Code Camp, be sure to download the slides and examples from the site.Read More
My MSDN Code Camp presentations and code samples are available for download on my website at http://www.jasongaylord.com/talks. The samples and slides were written for Visual Studio 2005 and ASP.NET 2.0 Beta 2. The talks include an Introduction to Visual Studio 2005 and ASP.NET 2.0, Membership for ASP.NET 2.0, Personalization for ASP.NET 2.0, and Web Parts for ASP.NET 2.0.Read More
If you have a large ASP.NET website, you may want to turn off compilation of your non-code ASP.NET pages. You can do this by setting the
CompilationMode property of the
Page directive to
Never. If you aren’t in the mood to check all pages, let ASP.NET decide. In the web.config file, set the
CompilationMode property in the
<pages /> section to
Auto. This will allow ASP.NET to evaluate each page and decide whether or not it should be compiled.