May 2009 - Posts
Typemock is launching a new product for ASP.NET developers – the ASP.NET Bundle - and for the launch they are giving out FREE licenses to bloggers and their readers.
The ASP.NET Bundle is the ultimate ASP.NET unit testing solution, and offers both Typemock Isolator and Ivonna, the ASP.NET Isolator add-on, for a discounted price.
ASP.NET Bundle launch giveaway:
For the ASP.NET Bundle launch Typemock are giving away free licenses to bloggers and their readers.
How do I get the free license?
Are you a blogger, webmaster, or internet columnist? Get your free license by helping Typemock launch their new ASP.NET Bundle, the ultimate ASP.NET unit testing solution.
Post the text below on your blog (as is, with links) and tell them about it . If you are in the first 60 to mail us after posting, your license will be on its way!
If you have an ASP.NET dedicated blog, you'll get a license automatically (even if more than 60 submit) during the first week of this announcement.
8 bloggers will also get an additional 2 licenses (each) to give away / raffle to their readers or friends.
A few simple requirements:
-
You must own a website, blog space or internet column, older than 2 months, or get permission from the owner of such a site.
-
Your post must include the text below (including the links) between *Begin* and *End*.
*Begin*
Unit Testing ASP.NET? ASP.NET unit testing has never been this easy.
Typemock is launching a new product for ASP.NET developers – the ASP.NET Bundle - and for the launch will be giving out FREE licenses to bloggers and their readers.
The ASP.NET Bundle is the ultimate ASP.NET unit testing solution, and offers both Typemock Isolator, a unit test tool and Ivonna, the Isolator add-on for ASP.NET unit testing, for a bargain price.
Typemock Isolator is a leading .NET unit testing tool (C# and VB.NET) for many ‘hard to test’ technologies such as SharePoint, ASP.NET, MVC, WCF, WPF, Silverlight and more. Note that for unit testing Silverlight there is an open source Isolator add-on called SilverUnit.
The first 60 bloggers who will blog this text in their blog and tell us about it, will get a Free Isolator ASP.NET Bundle license (Typemock Isolator + Ivonna). If you post this in an ASP.NET dedicated blog, you'll get a license automatically (even if more than 60 submit) during the first week of this announcement.
Also 8 bloggers will get an additional 2 licenses (each) to give away to their readers / friends.
Go ahead, click the following link for more information on how to get your free license.
*End*
Once you post this in your site, just drop them a line at asp@typemock.com with your name and the post URL to get your free license.
Hurry up – this offer is limited to the first 60 bloggers, or to ASP.NET dedicated bloggers who will post this in the first week.
Make sure to follow their Blog, Site or Twitter for updates on this event.
It’s finally out!
The LINQ Com C# (LINQ With C#) book that Luís and I wrote is out. Well, mostly Luís than I.
This book, published by FCA, is targeted at anyone that already knows C# 2.0 and wants to know learn the new features introduced with C# 3.0 that made possible LINQ (Language INtegrated Query). The examples in the book are written in C#, but Visual Basic get be get from the book’s site.
The book can be found here:
Unlike it happened on Windows XP, on Windows Vista and Windows 7, the search results window doesn’t have (by default) a column with the folder path of the found items. Instead, it has a column named Folder in the form of Folder name (folder’s containing folder path).
I don’t know the reason behind this decision, I just know that it makes hard to sort the found files by its path.
Fortunately, the folder path of the found items can be added to the list view by right clicking on any list column and selecting the folder path to be shown.
Unfortunately, I couldn’t find a way to make it permanent. I need to do that for every search.
Most enterprises backup their data on a regular basis and stored those backups for some amount of time.
But, beyond restoring last day’s backup or part of a previous recent backup, are these backups real useful? Will they be useful 3, 4, 5 or 10 years from now?
Nowadays, the tendency is to virtualize almost every machine which increases the probability of a successful restore in the future. But some software packages come with timed and online checking licenses and one might end up with a successful restore of an unusable system.
And what if the hardware to run the system (virtualized or not) no longer exists?
The solution is to backup the business data (instead of the system data) in a interoperable format like XML (that can contain both data and metadata).
The added benefit beyond disaster recovery is system or application migrations.
That doesn’t mean that systems don’t need to be backed up. They do, but only for operational purposes.
It is a good security practice to use Windows Authentication to connect to SQL Server because you don’t need to write the password on some configuration file or registry entry.
This practice also brings governance benefits. Managing users becomes part of domain administration and not part of each SQL Server instance’s administration.
But this becomes an hassle to users (in this context, the user is someone that needs to perform administration task of some kind – a SQL Server Management Studio user) who need to connect to databases using different credentials.
One workaround is using the runas command:
runas /user:DOMAIN\USERNAME "C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe"
But if you are working on an environment were there are several domains and your machine does not belong to the domain of the ser account you want to use, you’ll get the folloing error:
RUNAS ERROR: Unable to run - C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe
1787: The security database on the server does not have a computer account for this workstation trust relationship.
But not everything is lost. Because you want to make a remote connection, you can use the /netonly switch, and it works just fine:
runas /netonly /user:DOMAIN\USERNAME "C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe"
SQL Server Management Studio still shows all the databases in the server (unlike what happens if you connect from a machine logged in as the user you want to access to the SQL Server instance), but ApexSQL Edit will only show the databases that account has access to.