Archives
-
IIS Error Message: Snap-in failed to initialize
Oh I love errors! LOL…and I love posting about them because I learn something every time. With any issues comes solutions, always. You might not be able to find it the first time or the second time but over time, some way or another you’ll be lead to an actual solution. While working on an ASP.NET issue, I encountered an issue accessing an application. The error goes something like this:
-
No Visual Studio template found error
The last few blogs that I posted about were about errors and there should be no surprise this time as I'm posting another error that I encountered today while firing up Visual Studio 2008 at home. The error that I received was, there was "no Visual Studio template found" and regardless of what framework I picked when creating a new website or project, no template was shown. Take note that I'm also using Microsoft Vista which also added to the issue (as I'll discuss in a few).
-
Server tag "asp:ScriptManager" is ambiguous
I have encountered this error message in the past when I upgrade a few projects to 3.5 but it has been at least 3-4 months and found myself stuck with the same dilemma once again today. This error can be attributed to many things but mainly it comes down to web.config or ambigiouty in the references. Like my previous post, I would like to make another mental note as I know for sure that this won't be the last time that I will be seeing this error nor for anybody who upgrades to 3.5 that uses Ajax functionalities. After searching the web for answers, there was no definite response but after an hour of continuous searching, I was able to put all the information together which leads to the fix.
-
No love for VB?
I'm looking around on books that evolves around ASP.NET and I'm starting to see a common pattern among a lot of the books. In most cases, they are predominantly written in C# leaving no alternate code in VB. I know that C# is being pushed by a lot of developers to be a better choice (this is debatable), but I just don't understand why there is a favor towards a single programming language (C# in this case). I'm a VB programmer myself and I know that C# is pretty similar and shouldn't be hard to learn, but the same concern goes the other way around. If most technical books are written in VB, then I'm pretty sure that the C# community will have the same concern as well.
-
The type 'System.Web.UI.ScriptManager' is ambiguous
Given the error above and more information below:
-
Script module error when upgrading to 3.5
When I converted a project from 2.0 to 3.5 today, I got an error that appears from the Web.config.
-
Insertion of a page break in a repeater
I was in a situation where I need to break up the data into a separate page after a certain amount of records (in my case 3). I chose to use repeater as I have a full control of the HTML layout and how I want my form to appear in a print format. I posted my question in ASP.NET forums and to my delight received a working code after a full day of torture and doing search in Google. I thought I would share here the snippet that can be useful when a specific scenario arise. It is not a lot of code but it saved me another day of frustration. Now it's time to put it on the side and move on with new projects.
-
First post objective
I'm glad to be part of this great community and have the opportunity to blog with the best in the business. Since .NET has been introducing a lot of new features, it can be cumbersome to keep up with the latest changes. My goal herein my posts is about learning ASP.NET (cause I don't sincerely know it all) which includes topics relevant to problem solving, implementing features and/or give opinions about issues within the technology. I'll post as much as I can, and I hope to be an active participant in this community for years to come.