How to: Prepare a Database for Deployment From a Command Prompt by Using VSDBCMD.EXE shows how to upgrade the schema of a database on a remote server. However I encountered a problem this week running vsdbcmd.exe on a Windows Server 2008 R2 64bit machine:
vsdbcmd.exe /action:deploy /dd+ /manifestFile:Project.Database.deploymanifest An unexpected failure occurred: An attempt was made to load a program with an in correct format. (Exception from HRESULT: 0x8007000B)
This error normally implies that you’ve got a mismatch between 32bit and 64bit dlls. I’d copied the DLLs from my Windows 7 32bit development virtual machine, so that made some sense.
It was suggested I copy the DLLs from a 64bit machine, but unfortunately that had no effect. I then noticed that some of the sqlce dlls did appear to be 32bit-specific.
I then downloaded and installed both the 32 and 64bit versions of SQL Compact 3.5 SP2 on the server, and removed the original sqlce dlls that I’d copied along with vsdbcmd.exe.
That seems to have fixed the problem – vsdbcmd now executes correctly.
So the actual list of DLLs ended up copying to the server now that the SQL Compact files are already installed are:
- Extensions (folder)
6.30am – Woke up
6.40am – Ate breakfast with kids
6.50am – Logged in to MSDN and started downloading the release version of Visual Studio 2010!
Not a bad way to start the day :-)
- Support for the 2008 RDL schema in local mode.
- Support for ASP.Net AJAX (All page navigation and report interactivity is done with AJAX)
- Significantly improved browser compatibility.
- Usability and “look and feel” enhancements.
- Local mode now supports the same RDL features that are currently available in SQL Server 2008, including tablix, chart, gauge, and rich text.
- AsyncRendering now controls whether the initial processing of the report blocks the entire ASP.Net page, and nothing else.
- Can be loaded into a .NET 3.5 or a .Net 4.0 application.
- No more frames - ASP.Net postbacks are used to render the report.
Read more about the ReportViewer control in the MSDN Library.
One tool that I was lacking in my new role as a Senior Consultant for LobsterPot Solutions was a laptop computer. Back in my UniSA days, if you needed a laptop for a presentation or a conference you just borrowed one, so it was never a problem. Post-UniSA I borrowed my Mum’s nice Toshiba, or more recently the small (but capable) HP Mini Netbook that I got from [Tech-Ed last year]/2009/09/tech-ed-2009-friday.html).
Rob and I did a fair bit of research, compared brands and options (including the Sony Z-series which I see Nigel chose), and settled on the Dell Studio XPS 16 model. Being a “laptop-newbie” I particularly valued Rob’s good experience with his previous Dell laptop.
The XPS 16 comes with:
- Intel® Core™ i7-820QM Processor (1.73GHz, 4 Cores/8 Threads, turbo up to 3.06GHz, 8MB Cache)
- 8GB RAM
- 640GB HDD (will replace with SSD soon)
- 15.6” Screen
- ATI Mobility RADEON HD 4670 – 1GB
- Backlit keyboard
The CPU and RAM are similar to the [Hyper-V server I built]/2010/02/assembling-hyper-v-server.html) – though happily, while this CPU is also a Core i7, unlike it’s desktop cousin it doesn’t require a great whopping heatsink/cooler stuck on top (which could make shutting the lid a bit tricky!)
Some nice things I’ve discovered so far:
- It looks very nice, though the glossy surface does show up fingermarks very quickly.
- You can do “two-finger zooming” on the touch pad – great for Google/Bing maps.
- Windows 7 x64 runs very nicely.
- Rob noticed you can disable battery charging when on AC power.
- Doesn’t seem to get too hot (though the AC transformer does)
After having a quick play I was pleasantly surprised to find that Dell had shipped it with the latest BIOS firmware - that is refreshing. Nevertheless, after a precautionary backup to my Windows Home Server, I did a clean install of Windows 7 x64 Ultimate and am proceeding to load up all the various “mandatory” applications (Office, SQL Server, Visual Studio, etc).
I’m also thinking I might leverage Windows 7’s “boot to VHD” feature to have separate Win7 instances where I can try out pre-release/beta software without “polluting” my primary OS.
We chose the red ones, because a) they go faster (obviously!) and b) it kind of matches the red of the LobsterPot logo :-)