February 2007 Entries
SQL Server 2005 includes several new veiws to help developers fetch metadata about database objects. This has been possible in previous version of SQL Server, but required messy queries against the internal system tables or the use of some of the stock system procedures that shipped with SQL Server. The database schema we develop with at work is fairly large - ~2000 tables, ~4500 procs. I found myself using two of the most famous system procedures - sp_help and sp_helptext - to frequently lookup table and proc metadata. These are handy stored procedures, but sp_help lacks easy to read foreign key info...
At my day job, we're in the process of moving a sizable list of ASMX+WSE services to Fx3 and WCF (this is the first time I'm looking at WCF beyond playing with the sample). We're applying several lessons learned in the past and taking time to think through how we're implementing our service contracts. One of the great-great things about WCF is developers now define their contracts in code, and use tools to export the XSD Schema. namespace Brownsberger{ [ServiceContract()] public interface IProductService { [OperationContract] CreateProductResponse CreateProduct(CreateProductRequest request); } [MessageContract] public class CreateProductRequest { }; [MessageContract] public...
There are a lot of people out there having issues with this:
I did a number of things to get this working... some specific to Vista, and others not. I read several forum posts about tweaking WINS and NetBios settings on your NIC. I didn't have to do any of that. I'm not sure if all of these are required, here are my settings:
Turn off TCP/IPv6
Unblock Network Discovery in Windows Firewall
...