I have spent TWO(2) DAYS on this stupid error:

An exception of type System.Security.Principal.IdentityNotMappedException was thrown.  Additional exception information: Some or all identity references could not be translated.

when reinstalling Microsoft Office SharePoint Server 2007 (MOSS 2007). Well, scouring to the ends of Google-land, I didn't find a solution. From what I found never included #3 step below. I finally figured that problem out myself. For all with this error:

1. Delete/Remove all SharePoint databases.

2. Go into IIS and delete the "SharePoint Central Administration V3" site (if it didn't get removed during an uninstall).

3. MOST IMPORTANT!!! - Go into IIS and under "Application Pools" and delete "SharePoint Central Administration V3" (or be like me who wasted 2 freakin days).

If you don't follow #3, your install will fail every damn time in every scenario (Basic, Advanced - Complete, Web, Stand-Alone) and these installs/reinstalls can take a very LONG time.

Two (2) words: It ROCKS!!! I'm not saying that for promotion or any marketing, but that it's filled with TONS of info for small business. I know about OpenOffice and other office suites (like Google's), but from what I've learned and what you can do with Office 2007 and all around Office 2007, it's really an awesome app for businesses, not just for personal use or school.

I'm currently viewing the "Taking Your Business to the Next Level with Microsoft Dynamics GP" session with Jon Pratt. There's a lot of other sessions with great info. See you there...

Today I realized exactly how much I love to code. Like having the Event Logs emailed to me if an error occurs or checking the Event Logs from my website. I'm glad to have such an opportunity and chance to get to learn something new every single day I code and know that whatever I do or need, an answer is there. If not, then I get the chance to figure it out, get all excited about it, then post it and share to the world. So, I love programming and get to do it everyday is even more fun. Now to just complete all the work I just realized I now need to do...

I did a review this month of all of the popular products for easier web application development for ASP.NET 2.0 in Visual Studio 2005. With all of the irritating frustrations and advancements of features they provided, I found that ReSharper was the most "useful" tool. Reason? I like to work, not play and time management is crucial in my job. If I need to quickly format my code, all of the code in the project, I can. If I need to have "real-time" error analysis while typing my code, I can. ReSharper provides all the tools I need to ACTUALLY get work done. As far as CodeRush? I found myself playing with CodeRush than working. CodeSmith is a great tool for what it offers and Visual Assist X (as what the name implies) assists in the visuals of your code and lets you read code better. But when your need work done and need to code fast, ReSharper is the tool for speed demons. Now for the disappointments in ReSharper (it's not perfect yet)? There's no extensive support for XML usage, minor delay when loading large projects, and sometimes requires a reinstall when loading projects and the CPU reaches a constant 100% usage. Like I said, it's not perfect yet but VERY useful for what it offers. So, patience will be implied until these bugs are fixed or something better comes around...

Ok, Google (Gmail) is hosting our emails through "domain sharing". Basically, any emails being sent to raylinder@glacsy.com goes to Gmail and Gmail hosts it. My concern was SMTP from our website in ASP.NET 2.0. Yes, sound overwhelmingly exciting doesn't it? Well, there's is a way, the LONG and easier way or the short and painful way. LONG and easier way is, you build a SMTP class/control and namespace it to something like Glacsy.Net.WebMail then create a the SMTP assembly to accept parameters like From, To, BCC, Subject, Body. Then every page you want to send email, just map it to the class. Long time to build it, easy to use. I'm not getting into the short and painful way, you can just use your imagination. Below is some code on your page (yes, finally I'm including code):

Glacsy.Net.WebMail.SMTP("welcome@glacsy.com", someone@their-email.com, "bcc@some-one-else.com", "My Subject", "My body or message...");

using System.Net;
using System.Net.Mail;
using System.Text;

namespace Glacsy.Net
{
    public class WebMail
    {
        public static void SMTP(string from, string to, string bcc, string subject, string body)
        {
            MailMessage mailMsg = new MailMessage();
            mailMsg.From = new MailAddress(from);
            mailMsg.To.Add(to);
            mailMsg.Subject = subject;
            mailMsg.IsBodyHtml = true;
            mailMsg.BodyEncoding = Encoding.UTF8;
            mailMsg.Body = body;
            mailMsg.Priority = MailPriority.Normal;
            // Smtp configuration
            SmtpClient client = new SmtpClient();
            client.Credentials = new NetworkCredential("youremail@gmail.com", "yourpassword");
            client.Port = 587; //or use 465            
            client.Host = "smtp.gmail.com";
            client.EnableSsl = true;
            object userState = mailMsg;
            try
            {
                //you can also call client.Send(msg)
                client.SendAsync(mailMsg, userState);
            }
            catch (SmtpException)
            {
                //Catch errors...
            }
        }
    }
}

I've recently discovered a change in the SP1 for Visual Studio 2005 IDE. Below are solutions I found:

Problem -
When using Visual Studio Team Edition for Software Developers IDE with Visual Studio SP1 and ASP.NET AJAX RC installed, the Properties window becomes empty (completely blank) when viewing an ASP.NET control or any <tag> in Source View for a web app. Everything works fine when viewed in Design View. I've only recently installed SP1 & AJAX RC. There are no "extras/add-ons" installed for VS2005 IDE as I've just reinstalled Window Server 2003 EE last week. Just curious to know if there's a "user error" or a "ID10T error" (on my behalf) or if it's just a bug in the SP1 or AJAX RC installations. Note: Before the SP1 & AJAX RC install, everything worked fine as before and am not sure if it's SP1 or AJAX RC causing the issue as I've installed both around the same time before bug was discovered. Just let me know what's going on...

Solution -
I found the answer to my problem just in time from ScottGu's blog sent via RSS. When installing Visual Studio 2005 Service Pack 1, the Properties window gets disabled by default do to developer feedback. Apparently, more developers considered the Properties window a major annoyance (which I strongly disagree). You'll have to re-enable by "simply open the Tools->Options menu item and click the "Enable Property Grid in Source View" configuration option within the Text Editor->Html->Miscellaneous category". Hope this helps and thanks for the tip Scott...

I know there will be quite a few developers that may need this. The original post and be found here.

I'm apart of something. Something called .NET. And there's a community of .NET. Many communities of .NET. Billion dollar .NET. But there's this one particular .NET. A Community. It has a name. That name is Clearscreen. I'm not sure if it's me. But there's Spanish in it. Lots of Spanish. So you could say that I'm apart of a Spanish .NET. I don't know Spanish. But most of it is in Spanish. At least the English part of .NET is in Spanish. But the code of .NET at Clearscreen is mostly in English. Which I guess is good for me. They post the coolest things. In Spanish. If I knew Spanish, I could know those cool things. I think Spanish is a great language. There's many great languages. Like Navajo. Navajo is a Native American language. My girlfriend speaks Navajo. She's is a Navajo Native American. I know some Navajo like Aa'yah te'e. That means Hello. Navajo is great. And Spanish is great too. So you can say I'm apart of a Spanish .NET community who know some Navajo and speaks English. This post was inspired by http://www.clearification.com provided by a cool post at Clearscreen.

My girlfriend bought me a battery-powered desk waterfall with LED lights from Wal-Mart. It has a port for a 5V AC power adapter. So with all the old AC adaptors laying around the house and an extra USB wire (included with my DSL modem), I cut, connected, and duct-taped the wires. Then, plugged in the waterfall and I now have a USB powered waterfall on my desk. You can get the "LED illuminated rainfall fountain" from Wal-Mart for about $10.

I recently re-installed Windows Server 2003 EE (used as my workstation/developments) and then installed the rest of my software including Visual Studio 2005. After the installs and tweeks, I fired up VS2005 and started working on Glacsy.com. The next day I fired up VS2005 again and noticed there's no MRU's. So off I go to find a solution - Google... For days I searched for the answer then found http://geekswithblogs.net/glozano/archive/2006/11/13/96939.aspx by Gabriel Lozano-Morán. So I figured WinServer2003 disables MRUs by default, then enabled and now my system is near - perfect...

It seems (which I've just found out) that you can not install Adobe Premier Pro v2.0 unless you're using Windows XP w/ SP2 ONLY??? Just GREEAT!!! I'm using Windows Server 2003 Enterprise Edition (x86) for my developing web/windows forms apps. Well, without total defeat, time for Microsoft Virtual PC. hehe...

Wish me luck...

When reading data from a database using the Page_Load event and then updating the database, the data doesn't get updated as described here.

By including

if (!Page.IsPostback)

in before the reader allows data to be updated in other areas on the page/form. Below are examples:

Update doesn't work:
==================================================================

protected void Page_Load(object sender, EventArgs e)
{
      DataList1.DataBind(); 
}

protected void DataList1_UpdateCommand(object source, DataListCommandEventArgs e)
{
      SqlConnection sqlConn = new SqlConnection("connection");
      SqlCommand sqlComm = new SqlCommand("UPDATE blog_Postings SET title = @title, body = @body WHERE (id = @id)", sqlConn);

      sqlComm.Parameters.Add(new SqlParameter("@id", SqlDbType.Int));
      sqlComm.Parameters["@id"].Value = intID;
      sqlComm.Parameters.Add(new SqlParameter("@title", SqlDbType.NVarChar));
      sqlComm.Parameters["@title"].Value = strTitle;
      sqlComm.Parameters.Add(new SqlParameter("@body", SqlDbType.NVarChar));
      sqlComm.Parameters["@body"].Value = strBody;

      sqlComm.CommandType = CommandType.StoredProcedure; 

      sqlConn.Open();
      sqlComm.ExecuteNonQuery();
      sqlConn.Close();
      sqlComm.Dispose();

      DataList1.EditItemIndex = -1;
      DataList1.DataBind();
}

When the DataList is updating, the function protected void Page_Load(object sender, EventArgs e) runs again/refreshes which retrieves the old values in the database.


Update works:
==================================================================

protected void Page_Load(object sender, EventArgs e)
{
      if (!Page.IsPostBack)
      {
            DataList1.DataBind();
      } 
}

protected void DataList1_UpdateCommand(object source, DataListCommandEventArgs e)
{
      SqlConnection sqlConn = new SqlConnection("connection");
      SqlCommand sqlComm = new SqlCommand("UPDATE blog_Postings SET title = @title, body = @body WHERE (id = @id)", sqlConn);

      sqlComm.Parameters.Add(new SqlParameter("@id", SqlDbType.Int));
      sqlComm.Parameters["@id"].Value = intID;
      sqlComm.Parameters.Add(new SqlParameter("@title", SqlDbType.NVarChar));
      sqlComm.Parameters["@title"].Value = strTitle;
      sqlComm.Parameters.Add(new SqlParameter("@body", SqlDbType.NVarChar));
      sqlComm.Parameters["@body"].Value = strBody;

      sqlConn.Open();
      sqlComm.ExecuteNonQuery();
      sqlConn.Close();
      sqlComm.Dispose(); 

      DataList1.EditItemIndex = -1;
      DataList1.DataBind();
}

So, as you can see by not validating the postback will causes data not to update which will lead into hours of frustration. Enjoy...

(Posted using Windows Live Writer)

Just found the time to install Window Live Writer. Yes, it's awesome like everyone has been saying - using it to post this message. This means I'll be enabled to post much more often.

Now to figure out why my datalist isn't updating data in my web app (but it works everywhere else on the damn site, lol)...

This is a different post, a “not so technical“ for the least. With GBN Beta releasing on 9/28/2006, I've started seeing the business support degrade with Glacsy's affiliates. Is Glacsy being left-out, used, over-runned, depreciated from it's hard work supporting it's affiliated businesses? I hope not. As a new company, the first company I've supported, I've begun to see the “circle of friends” rather than individuals (Business owners or CEO's) running their company as a Company. Instead, there's the “yeah, I have a business, but I'm not really treating it as one” relationships that has sprouted around Glacsy. Allthough, I do enjoy the concept of the under-estimated possibilities that are miss-judged by many people towards Glacsy. I've recently learned that even if you may “see” a great negociated deal/opportunity or even finalize one, it may be a plan to keep you down and that's the true joy of doing business with “circles of friends”. I've learned that when involved in this kind of “business infrastucture“, they tend to continue the routine not only with each other, but with everyone and thing around them.

There's a business culture involved into these meanings, a culture that started as an organized, successful, well-established community of people with traditions dated back since time began. It's sad to see today, that that solid involvement has degraded enourmously. For the next big step, I'll be thinking “outside and all around the box”. For those targeted by this post, Desperation is NOT the Key to Success...

Finished the design of G3 and it's feature/sections (except Glacsy Models, reserved for last). Using Blogger.com as a temp solution for Glacsy.com for updates and until G3 is ready.