1. Open the Skype Options window by clicking Tools in the top menu Options.
2. Click on "Notifications" on the left hand menu
3. Click on "Alerts & Messages"
4. Under "Show messages about..." uncheck all options.
5. Restart Skype
How to turn off Skype Advertising Pop-Ups
Skype has an annoying habit of popping up little advertisements which clutter the user interface and have animations that I find distracting. Here is how to get rid of them.
Steps:
1. Open the Skype Options window by clicking Tools in the top menu Options.
2. Click on "Notifications" on the left hand menu
3. Click on "Alerts & Messages"
4. Under "Show messages about..." uncheck all options.
5. Restart Skype
1. Open the Skype Options window by clicking Tools in the top menu Options.
2. Click on "Notifications" on the left hand menu
3. Click on "Alerts & Messages"
4. Under "Show messages about..." uncheck all options.
5. Restart Skype
The Microsoft Visual Studio Remote Debugging Monitor has been closed on the remote machine.
I was having an annoying problem with vs2008 where when I tried to debug I would sometimes get this error message:
The fix: The most reliable way to get around this I've found is to set your startup projects platform to "x86" in the project settings. This removes the need for visual studio to silently do remote debugging.
"Error while trying to run project: Unable to start debugging.But I wasn't remote debugging! It turned out the reason this is happening is because visual studio is a 32 bit application but I'm running a 64 bit OS. When I hit F5 I'm launching a 64 bit application so for visual studio to debug it it has to silently start remote debug to bridge the gap.
The Microsoft Visual Studio Remote Debugging Monitor has been closed on the remote machine."
The fix: The most reliable way to get around this I've found is to set your startup projects platform to "x86" in the project settings. This removes the need for visual studio to silently do remote debugging.
How to select a list of every table in a sql server database and row count in each table
How to select a list of every table in a sql server database and row count in each table. I've found this very handy over the years when doing data migrations and comparing databases.
Tested on SQL Server 2005 & 2008
CREATE TABLE #temp (
table_name sysname ,
row_count int,
reserved_size varchar(50),
data_size varchar(50),
index_size varchar(50),
unused_size varchar(50))
SET NOCOUNT ON
INSERT #temp
EXEC sp_msforeachtable 'sp_spaceused ''?'''
SELECT a.table_name,
a.row_count,
count(*) as col_count,
a.data_size
FROM #temp a
INNER JOIN information_schema.columns b
ON a.table_name collate database_default
= b.table_name collate database_default
GROUP BY a.table_name, a.row_count, a.data_size
ORDER BY table_name --CAST(Replace(a.data_size, ' KB', '') as integer) desc
DROP TABLE #temp
Tested on SQL Server 2005 & 2008
CREATE TABLE #temp (
table_name sysname ,
row_count int,
reserved_size varchar(50),
data_size varchar(50),
index_size varchar(50),
unused_size varchar(50))
SET NOCOUNT ON
INSERT #temp
EXEC sp_msforeachtable 'sp_spaceused ''?'''
SELECT a.table_name,
a.row_count,
count(*) as col_count,
a.data_size
FROM #temp a
INNER JOIN information_schema.columns b
ON a.table_name collate database_default
= b.table_name collate database_default
GROUP BY a.table_name, a.row_count, a.data_size
ORDER BY table_name --CAST(Replace(a.data_size, ' KB', '') as integer) desc
DROP TABLE #temp
Visual Studio Hanging
Do get lots of hangs in Visual Studio where the window fails to redraw when scrolling, some windows don’t paint – and then VS finally hangs. It appears this is because you are hitting the default 10,000 GDI object per process limit. This seems to happen to me quiet often when viewing xaml files (in vs2008).
You can see the GDI Object count in Process Explorer or if Task Manager - by clicking on the view -> select columns menu and ticking GDI Objects.
You can't fix this as far as I know but you can delay the inevitable by increasing the limit.
See this link for information on how to change the GDIProcessHandleQuota limit in the registry: http://msdn.microsoft.com/en-us/library/ms724291(VS.85).aspx
I set the limit to 15,000 on my windows 7 64 bit desktop with 4 gig of ram and haven't had any issues.
For more detailed information on GDI Objects see this page: http://blogs.technet.com/markrussinovich/archive/2010/03/31/3322423.aspx
You can see the GDI Object count in Process Explorer or if Task Manager - by clicking on the view -> select columns menu and ticking GDI Objects.
You can't fix this as far as I know but you can delay the inevitable by increasing the limit.
See this link for information on how to change the GDIProcessHandleQuota limit in the registry: http://msdn.microsoft.com/en-us/library/ms724291(VS.85).aspx
I set the limit to 15,000 on my windows 7 64 bit desktop with 4 gig of ram and haven't had any issues.
For more detailed information on GDI Objects see this page: http://blogs.technet.com/markrussinovich/archive/2010/03/31/3322423.aspx
Grant exec on all stored procs
Its so annoying that sql server doesn't come with a default role to just have exec permissions on all stored procs. Oh well.
I love this little stored proc. Its usually a good idea to prevent your database user from having direct read/write access to your database to tricks some nasty hacker might throw at you - Its usually good practice to give your user just access to the stored procedures. I usually run it at the end of every release to ensure the user can exec any stored proc.
use master
go
create procedure sp_grantexec(@user sysname,@pattern sysname = NULL,@debug int = 0)
as
set nocount on
declare @ret int
declare @sql nvarchar(4000)
declare @db sysname ; set @db = DB_NAME()
declare @u sysname ; set @u = QUOTENAME(@user)
set @sql ='select ''grant exec on '' + QUOTENAME(ROUTINE_SCHEMA) + ''.'' +
QUOTENAME(ROUTINE_NAME) + '' TO ' + @u + ''' FROM INFORMATION_SCHEMA.ROUTINES ' +
'WHERE OBJECTPROPERTY(OBJECT_ID(ROUTINE_NAME),''IsMSShipped'') = 0'
if @pattern is not null
set @sql = @sql + N' AND ROUTINE_NAME LIKE ''' + @pattern + ''''
if @debug = 1 print @sql
else
exec @ret = master.dbo.xp_execresultset @sql,@db
If @ret <> 0
begin
raiserror('Error executing command %s',16,1,@sql)
return -1
end
I love this little stored proc. Its usually a good idea to prevent your database user from having direct read/write access to your database to tricks some nasty hacker might throw at you - Its usually good practice to give your user just access to the stored procedures. I usually run it at the end of every release to ensure the user can exec any stored proc.
use master
go
create procedure sp_grantexec(@user sysname,@pattern sysname = NULL,@debug int = 0)
as
set nocount on
declare @ret int
declare @sql nvarchar(4000)
declare @db sysname ; set @db = DB_NAME()
declare @u sysname ; set @u = QUOTENAME(@user)
set @sql ='select ''grant exec on '' + QUOTENAME(ROUTINE_SCHEMA) + ''.'' +
QUOTENAME(ROUTINE_NAME) + '' TO ' + @u + ''' FROM INFORMATION_SCHEMA.ROUTINES ' +
'WHERE OBJECTPROPERTY(OBJECT_ID(ROUTINE_NAME),''IsMSShipped'') = 0'
if @pattern is not null
set @sql = @sql + N' AND ROUTINE_NAME LIKE ''' + @pattern + ''''
if @debug = 1 print @sql
else
exec @ret = master.dbo.xp_execresultset @sql,@db
If @ret <> 0
begin
raiserror('Error executing command %s',16,1,@sql)
return -1
end
Script to kill all connections to a database
When restoring/moving databases its a pretty common requirement to kill all the connections to the database in question otherwise you can't get a lock on it. Killing all the connections to a database can be a pain though if you have to use the UI. This script is much quicker and can be a time saver. If you’re super keen you could modify the script to make it a stored procedure so it’s always ready to go. If you do want to use the UI here is a blog post on how to do it.
--
-- Kill connections to a given sql server database
--
declare @execSql nvarchar(MAX), @databaseName varchar(100)
set @databaseName = '<your database name here>'
set @execSql = ''
select @execSql = @execSql + 'kill ' + convert(char(10), spid) + ' '
from master.dbo.sysprocesses
where db_name(dbid) = @databaseName
and
DBID <> 0
and
spid <> @@spid
exec(@execSql)
--
-- Kill connections to a given sql server database
--
declare @execSql nvarchar(MAX), @databaseName varchar(100)
set @databaseName = '<your database name here>'
set @execSql = ''
select @execSql = @execSql + 'kill ' + convert(char(10), spid) + ' '
from master.dbo.sysprocesses
where db_name(dbid) = @databaseName
and
DBID <> 0
and
spid <> @@spid
exec(@execSql)
A better way to declare your ValueConverters in XAML
Generally most people define a resource like this "<conv:AdditionConverter x:Key="AdditionConverter" />
This is OK but it’s fairly verbose and leads to converters being defined all over the place. An alternative is to use a MarkupExtension to minimize the amount of XAML code required. E.g.:
This approach has an added advantage of ensuring that all your converters are singletons.
This is OK but it’s fairly verbose and leads to converters being defined all over the place. An alternative is to use a MarkupExtension to minimize the amount of XAML code required. E.g.:
public class AdditionConverter : MarkupExtension, IValueConverter
{
private static AdditionConverter _converter;
public object Convert(object value, Type targetType,
object parameter, System.Globalization.CultureInfo culture)
{
// convert and return something
}
public object ConvertBack(object value, Type targetType,
object parameter, System.Globalization.CultureInfo culture)
{
// convert and return something (if needed)
}
public override object ProvideValue(IServiceProvider serviceProvider)
{
if (_converter == null)
_converter = new AdditionConverter();
return _converter;
}
}
Doing this you no longer need to define a resource as the XAML parser knows how to ask the markup extension to supply the converter. You end up with a syntax like this:
{Binding Converter={conv:MyConverter}}
This approach has an added advantage of ensuring that all your converters are singletons.
Taking it further: Making a wrapper base class
This article explains a generic markup extension class that hides the MarkupExtension implementation details and makes the process above even easier.
This article explains a generic markup extension class that hides the MarkupExtension implementation details and makes the process above even easier.
ConverterMarkupExtension.cs
using System;
using System.Windows.Data;
using System.Windows.Markup;
namespace sfc.Converters
{
[MarkupExtensionReturnType(typeof(IValueConverter))]
public abstract class ConverterMarkupExtension :
MarkupExtension where T : class, IValueConverter, new()
{
private static T _converter;
public override object ProvideValue(IServiceProvider serviceProvider)
{
if (_converter == null)
{
_converter = new T();
}
return _converter;
}
}
[MarkupExtensionReturnType(typeof(IMultiValueConverter))]
public abstract class MultiConverterMarkupExtension :
MarkupExtension where T : class, IMultiValueConverter, new()
{
private static T _converter;
public override object ProvideValue(IServiceProvider serviceProvider)
{
if (_converter == null)
{
_converter = new T();
}
return _converter;
}
}
}
There are 2 classes here, one for IValueConverter's and one for IMultiValueConverters.
You can then modify your classes to inherit from this class and they nolonger need to worry about implementing MarkupExtension E.g.:
You can then modify your classes to inherit from this class and they nolonger need to worry about implementing MarkupExtension E.g.:
public class AdditionConverter : ConverterMarkupExtension<AdditionConverter>
{
public object Convert(object value, Type targetType,
object parameter, System.Globalization.CultureInfo culture)
{
// convert and return something
}
public object ConvertBack(object value, Type targetType,
object parameter, System.Globalization.CultureInfo culture)
{
// convert and return something (if needed)
}
}
How to login to sql server using windows authentication over a VPN
This only applies to people that want to connect to a SQL Server instance over VPN to a domain that doesn't have a trust relationship with the source domain and don't want to have to use remote desktop. The method described below will allow you to access the SQL database seamlessly as if it were a database insist your domain.
1) Open a command prompt window
2) runas /user:"domain\user" /netonly "c:\program files\microsoft sql server\100\tools\binn\vsshell\common7\ide\ssms.exe" - replacing "domain\login" with your login details obviously
3) The command prompt with ask for "domain\login"'s password
4) SMSS will then run and you can connect to the database over VPN using the Windows Authentication option.
1) Open a command prompt window
2) runas /user:"domain\user" /netonly "c:\program files\microsoft sql server\100\tools\binn\vsshell\common7\ide\ssms.exe" - replacing "domain\login" with your login details obviously
3) The command prompt with ask for "domain\login"'s password
4) SMSS will then run and you can connect to the database over VPN using the Windows Authentication option.
Generic EventArgs
This has been done before but I think this is a cool tip that can save a heap of time and reduce the number of classes in your app.
There are a lot of times when you want to raise a quick event and just simply pass an value type or object as part of the EventArgs parameter. Instead of having to create separate EventArgs for every event you want to raise, we can create an EventArgs class that uses generics.
Usage:
...
You can wire up the SomeIntEvent event and I will be able to access eventArgs.Value
There are a lot of times when you want to raise a quick event and just simply pass an value type or object as part of the EventArgs parameter. Instead of having to create separate EventArgs for every event you want to raise, we can create an EventArgs class that uses generics.
public class EventArgs : EventArgs
{
public EventArgs(T value)
{
Value = value;
}
public T Value { get; set; }
}
Usage:
public event EventHandler<EventArgs<int>> SomeEventWithIntArg;
...
if (SomeEventWithIntArg != null)
{
SomeEventWithIntArg(this, new EventArgs<int>(123));
}
You can wire up the SomeIntEvent event and I will be able to access eventArgs.Value
SomeEventWithIntArg += OnSomeEventWithIntArg;
void OnSomeEventWithIntArg(object sender, EventArgs<int> eArgs)
{
int i = eArgs.Value;
}
WPF Xceed Grid: How to prevent/disable validation for objects that implement IDataErrorInfo
From the Xceed documentation:
"Built-in support for IDataErrorInfo provides business-object level validation that can be used in combination with validation rules.
Unless the ValidationRules collection is cleared, it will always contain an ExceptionValidationRule and DataErrorValidationRule. If the DataErrorValidationRule is excluded from the collection of validation rules, validation errors reported by IDataErrorInfo will be ignored. "
The solution is to manually loop over the columns and clear the validators
foreach(Column c in grid.Columns)
{
c.CellValidationRules.Clear();
}
Subscribe to:
Posts (Atom)