Thanks God, I didn't have to do VB6 for a long time.
But apparently you can now use the Visual Studio 2015 (or 2013) to work on your legacy projects.
To get more information on this extension, visit http://vbvs.cloudapp.net/
If you are like me connecting to various database sever with your laptop, after a couple of months, you find your "Connect to Server" dialog box filled with many connections not useful anymore.
For a long time, it has been complex to delete the unwanted connections but since SQL Server 2012 it is actually quite easy even if poorly documented!
The trick to delete the dead servers from the list is to select the name you want to delete either via mouse or via keyboard and press the delete key on the keyboard. Note that the text in the box will remain to your last selection even after delete.
The compression of backup in SQL Server has been supported since the release of 2008 R2. But I was surprised that this feature is not enabled by default!
To discover if your server has this feature currently set, you can run this small query:
SELECT value FROM sys.configurations WHERE name = 'backup compression default'
If the value returned is 1, then compression is already enabled. If the returned value is 0 and you want to enable the feature, you can do it by running this query:
EXEC sys.sp_configure 'backup compression default', 1
That will default all the backup (otherwise specified) to compress backups.
Note that as stated in Features Supported by the Editions of SQL Server 2014, the Express nor the Web editions support this feature.
I had one database in particular that the size of the backup was 3.5gb uncompressed. After enabling that feature, the size of the backup went down to 850mb. Your mileage may vary!
Of course this setting is also available if you open the Properties of your server (under Database settings).
Finally, it is also available to the backup command line. But I really recommend setting it at the server level so that all backups can automatically benefit from this feature.
This is the first article of 2016! Happy New Year.
Sometimes, when building applications, you need to warn users that something just happened but this warning doesn’t always have to be intrusive. In those occasion, a modal message box is not appropriate.
This is exactly what this article is about: showing very simple non-blocking notifications from a WPF application. I will even provide you links to other more complete, fancier and complex components to use (but still free).
If you are interested by that article, have a look at http://emoreau.com/Entries/Articles/2016/01/WPF-application-notifications.aspx
I really hope that I won't surprise anybody saying that SQL Server 2016 is just around the corner. It is now in technical preview if you have a spare machine (or a VM) to test it. The publicly available CTP is available from http://www.microsoft.com/en-ca/server-cloud/products/sql-server-2016/.
A free e-book is also available from http://blogs.msdn.com/b/microsoft_press/archive/2015/12/22/free-ebook-introducing-microsoft-sql-server-2016-mission-critical-applications-deeper-insights-hyperscale-cloud-preview-edition.aspx. They even have a smaller PDF version optimized for mobile reading.
I just published my last article for 2015.
Embedding a component as a resource in an application simplifies the distribution because you have less resources (files) to distribute.
A couple of months ago, I have shown how to embed a font into a WPF application. But we are not limited to fonts. DLLs from Class library can be embedded as well but it is a bit more complex to use them.
This month, I will show you how to embed a .Net DLL into a .Net application. I believe that this trick can be useful in very specific situation. But for large applications, I would never recommend to use this solution!
You can read this article from http://emoreau.com/Entries/Articles/2015/12/Embedding-a-DLL-in-a-Net-application.aspx
I just finished rewriting an article I have written in 2007 about licensing a .Net application.
The original article still has a lot of reads and generates a lot of questions. The questions are mostly because the sample I wrote at that time was misleading and contained both the client application and the key generation parts.
I have recreated the sample in 3 different projects (a common class library, a test project and a key generation project). It should be easier for you to understand what goes where!
You can read it from http://emoreau.com/Entries/Articles/2015/11/Licensing-a-Net-application--2015-edition.aspx
I am just back from a week in Redmond for the annual MVP Summit. I have met a lot of friends over there.
The only thing I can tell you is not to miss the Microsoft Connect() online and free event that will be held November 18-19. Last year, they made some great announcement and from what I read between the lines, it should be as exciting this year.
You can check the agenda by going to http://connect2015.visualstudio.com/
Since yesterday, I wasn't able to open Excel files located on the network which were previously running just fine.
I was receiving errors saying that the file was corrupted or the Excel splash screen was simply freezing trying to open the file.
To add to this strange issue, the same file when copied on my desktop was opening just fine!
I haven't changed anything on my computer. I even tried a Office 2016 repair. So surely one of the Windows Update pushed automatically to my Windows 10!
I have been able to fix my issue by following the steps listed on https://forum.openoffice.org/en/forum/viewtopic.php?f=15&t=42387 (even if I don't have Open Office installed!).
Lately, I had remote users testing one of my application. These users were not SnagIt users. They asked me to add a button to the application that will automatically create an email and attach the snapshot just taken.
So that was my inspiration for this month article which you can read from http://emoreau.com/Entries/Articles/2015/10/Taking-a-snapshot-of-a-screen-in-WPF.aspx.