So I have a problem, just a small one, when I go to any Passport/Live site and sign in, it fails. Only the first time, second time always in. Nothing serious I can work, but I thought maybe I should log this with Microsoft and maybe they can fix it? Since it is happening across multiple machines I am sure it's an account issue.

So off I log the call with all kinds of info (including I use Vista solely now on my work and home machines) and go though a few simple check emails. Annoyingly I get a new person on each email. Maybe I am spoilt from partner based support where the same person responds and they know whats going on, but getting a new person who is obviously not checking what has been done before and simply sending crap is getting too much. The last email broke the camels back. Why?

THEY TOLD ME TO UNINSTALL IE7! I mean for fucks sake, it's been out for year and is a flag ship product for Microsoft and support thinks it's the cause!?!? Worst is (and bonus points for you if you picked this up) Vista ships with it, there is no uninstall back to IE 6!?!I've attached a screenshot of the email in case you think I am crazy.

 

In my previous post I spoke about some of the new features in 3.5. For ASP.NET though there is more goodness coming in the form of the ASP.NET 3.5 Extensions package. This package contains some interesting bits I want to highlight.

• ASP.NET MVC: This model view controller (MVC) framework for ASP.NET provides a structured model that enables a clear separation of concerns within web applications, and makes it easier to unit test your code and support a TDD workflow. It also helps provide more control over the URLs you publish in your applications, and more control over the HTML that is emitted from them.
• ASP.NET Silverlight Support: With the ASP.NET 3.5 Extensions release we'll deliver support for easily integrating Silverlight within your ASP.NET applications.  Included will be new controls that make it easy to integrate Silverlight video/media and interactive content within your sites.
• ADO.NET Data Service (codename "Astoria"): In parallel with the ASP.NET Extensions release we will also be releasing the ADO.NET Entity Framework.  This provides a modeling framework that enables developers to define a conceptual model of a database schema that closely aligns to a real world view of the information.  We will also be shipping a new set of data services (codename "Astoria") that make it easy to expose REST based API endpoints from within your ASP.NET applications.

There are a few more and Scott Guthries post will be good to cover if you are interested (all the info above is from him).

Now starting with Silverlight support thats a no brainer really. If your market is developers wanting great tools, then making them edit HTML to get your new platform is a little tougher than need be. The MVC is a nice thing if you believe the information on it (I haven't used it yet myself) but it basically is bringing a lot of the CCF/CAB ideas to the web in a elegant way. Lastly Astoria is a great technology (I almost built my own for a project but beta 1 came out and saved me from that) which gets your data from within the black box of servers on to the web in a way it can be consumed by client applications easily. Obviously performance doesn't compare to ADO.NET directly but if you don't have access to the server this is the way to share information.

My first MSCRM 4.0 upgrade was last night and so was my first MSCRM 4.0 issue. The issue after upgrading MSCRM and going to the site was "System.Data.SqlClient.SqlException: Invalid object name 'Entity'.". Screen shot is attached to the post if you want to see that.

Straight away you can see it is a SQL error, so I whipped out SQL profiler to see what is going on. I first limited to the _MSCRM and _METABASE databases (remember this is an upgrade) and started to watch what is happening. What I noticed is that it is running a "select * from entity" so entity must be a table or view. Checking the DB though I can't find it and running the select statement myself also failed. I also noticed that the _METABASE is not being called at all.

So using deployment manager I created a new tenant to see what that looked like. First thing I noticed is no _METABASE for the new tenant, and that if I ran the select statement in the new tenant DB myself it worked. So I look through that and what do I find a table named entity. But wait whats this before it? Normally tables are prefixed by dbo this isn't it's prefixed by metabase something or other, and then I remembered my SQL 2005 training on schemas.

See MSCRM 4.0 doesn't need 2 databases anymore since it uses schema's to put both the metabase and data in one database and can control the security seperately on that! This is also why SQL 2000 is not support, since it doesn't have schemas (atleast one of the reasons).

To resolve this I made sure the network service account (since we upgraded with that) had the same permissions on the original DB as on the new tenant DB and viola it worked!

Since the Excel source component in SSIS (2005) doesn't support the XLSX formats from Excel 2007 you kinda have to kiss that away (hopefully SSIS 2008 is better). So to load it you can use ODBC to create a system or user DSN to the XLSX file (office 2007 installs the ODBC drivers needed) and then using the data source reader component connect to the data source and viola! XLSX goodness and a fraction of annoyance.

I must admit that it seems slow though, but I am not sure if that is because I never needed to load 200000 records out of Excel before our my laptop has enter the Christmas spirit mode already.

If you have any better ideas or ways of doing this, I would love to hear about it.

Update: This may also be of help to some people, drivers for OleDB etc...
http://www.microsoft.com/downloads/details.aspx?familyid=7554F536-8C28-4598-9B72-EF94E038C891&displaylang=en

It is definately the size of the spreadsheet which is killing it. Made a new one with one record and it works fine.

One thing about being a developer is that at some point you will have to work with databases/datastores. It's a fact of life (like death and taxes). The thing about these databases is that they all have connections strings to get to them, but the problem is how do you get the connection string? A popular website is http://www.connectionstrings.com/ which lists them and you can then copy, paste and modify those for your own needs.

However there is a problem with this, in that it's open to errors during the modification (assuming you can copy and paste without error) and that there is no nice test system for your environment. Well fear not, Windows (I've known about this since Windows 2000 and can confirm it works on XP, Vista and 2003 fine) has a great feature for finding out connection strings, and testing them.

To do this you create a new empty file somewhere (desktop is good, cause you can go right click New -> Text Document). The trick is to make sure the file extension is udl (i.e. connection.udl). Now you can double click this file and using the (possibly) familiar connection wizard/odbc thing to set and test the values the values:
Once you click OK the window disappears.

So what good is that? Well if you now open that file in notepad you'll find the connection string in plain text right there! With all the right values for your environment! Anyway happy connecting!

Update 10 Jan 2008: If you are doing this on x64 machines and getting issues this may help: http://blogs.msdn.com/snehadeep/archive/2008/01/10/running-a-32-bit-data-link-properties-udl-in-64-bit-box.aspx

For the sake of the series I am going to just highlight a few points. For real concrete stuff see:

• http://dotnetwithme.blogspot.com/2007/05/what-new-in-net-35.html
• http://msdn2.microsoft.com/en-us/library/bb332048(VS.90).aspx
• http://blogs.msdn.com/tims/archive/2007/07/27/what-s-new-in-wpf-3-5-here-s-fifteen-cool-features.aspx

There is a lot of new language features in 3.5, most important to highlight for this series is LINQ. Moving along to the more shiny information there is significant work put into integration of AJAX, WPF (XBabs support in Firefox, can work with cookies now), WCF (more WS* support, general syndication support, special model for web development,  and Silverlight. WCF + WF and WCF + AJAX now play very well together (lots of support for each other now). There is also support for new cryptography stuff (nice), peer to peer development. Interesting WinForms now supports the same model as ASP.NET for authentication.

All coming 2008!
Next Game
Next Project (not a game!)
And in the same vein as the next project, something a little different.

I like it all! In fact I am a tingle of excitement over it.

MSCRM 4.0 is now RTM!

Read more http://blogs.msdn.com/mscrmfreak/archive/2007/12/16/microsoft-dynamics-crm-4-0-hits-rtm.aspx

So after letting the auto tagger run all last night I now have my collection of music in a decent state. Next is the cleaning up of the collection. To do that I went and downloaded Media Library Organiser plugin. This great plugin renames files, builds a neat folder structure and removes duplicates. You can specify what the structure is (by default [Artist]\[Album]\[Track No] [Title].[File Extension]) and you can turn on/off the duplicate removal etc... Since this is all tagged base you desperately need to make sure your tags are done right first. This takes just a few minutes for thousands of audio files to be cleaned up.

WinAmp 5.5 was release recently with a great new plug-in called AutoTag. This plugin samples your music (the music itself, not the tags, not the file or filename, the actual music) then sends that to Gracenote who identify it and send all the tag information back so any music WinAmp can play (including music videos) gets correctly tagged and sorted.

Now add the album art download plug-in and your MP3 collection is looking great :)

These two features (and the revised layout, and outlook like popups) have made me a winamp fan again (after a few years of using Windows Media Player).

Get it from Winamp.com!