View Complete Post
I receive the subject error when I attempt to update a simple SQL database that I've created in Visual Web Developer 2005 Express Edition.ÃÂ I also have SQL Server 2005 Express Edition installed.ÃÂ I'm running XP SP3.
The database has one table called Customers with the following 5 fields: CustomerID (int) & primary key, FirstName (varchar(50)), LastName (varchar(50)), CreditLimit (smallmoney) and CustomerSince (smalldatetime).ÃÂ I've added about a dozen records to the table.
I can display the table in the web site and select records.ÃÂ However, after I add editing and deleting and attempt to update an edited record I receive the subject error which is pasted at the end of this question.ÃÂ Thinking my installation of SQL Server 2005 was the problem, I uninstalled and reinstalled.ÃÂ Still got the error.
NOTE:ÃÂ I have created the same database on a virtual machine also running XP SP3 with the Express Edition products mentioned above.ÃÂ The table updates with no error.
So I'm thinking the error message is probably not directly related to a SQL problem but some system problem that is on my host computer but not on my virtural machine.
I am trying to deploy through webmatrix but my system Proxy server configuration is not being used. I assume that webmatrix would detect the proxy server settings and use that for the msdeploy calls under the hood. Can anyone confirm this is a know issue?
New spatial data support in SQL Server 2008 opens the door to mapping and querying geometric and geographic data, allowing you to build exciting new applications.
MSDN Magazine February 2009
We take a look at planned support for parallel programming for both managed and native code in the next version of Visual Studio.
Stephen Toub and Hazim Shafi
MSDN Magazine October 2008
In this new column, Brian Randell begins his long look at how to extend and enhance Visual Studio Team System.
Brian A. Randell
MSDN Magazine January 2007
SQL Server 2005 includes several important improvements to the Transact-SQL (T-SQL) language. One added feature is a new kind of trigger that fires when data definition language (DDL) statements run.
MSDN Magazine May 2006
XML is becoming the ubiquitous data format on the Web, and XML support in SQL Server is evolving to meet the additional demand. Using XML, SOAP, HTTP, and SQL Server, you can now build powerful Web Services easily. To show just how simple it is with SQLXML 3.0, this article walks the reader through the process step by step, from setting up a virtual directory enabling data access via HTTP to executing queries and building Web Services. Finally, the author illustrates the creation of two Web Services clients-one with C# that works with the Microsoft .NET Framework and one with the SOAP Toolkit 2.0 for anyone still using earlier development tools.
MSDN Magazine May 2002
Handheld device users need to be able to synchronize with a main data store when it's convenient and, preferably, when the back-end database server isn't busy. SQL Server 2000 Windows CE Edition allows you to build a traveling data store that can be displayed and run on a variety of devices. SQL Server CE supports a subset of the full SQL Server package, and can be used as a standalone server or in tandem with SWL Server and IIS. The architecture of SQL Server CE, along with data manipulation, synchronization, and connectivity issues, are discussed in this article. Topics such as making your data public, choosing the right type of replication, and handling errors are also covered.
Paul Yao and David Durant
MSDN Magazine June 2001
Experienced a really strange problem today. I added a jquery script to my MVC application to collapse sections of a View (via divs).
Pretty standard stuff, he showed me the script working before hand and it works.
However any time I would run my MVC app via Visual Studio the script would not work. I changed browsers, re-imported the code from source control and basically me and my co-worker banged our heads together for some time trying to figure out why the exact same code was running different on two machines.
Publishing the MVC app to our web server and running worked for both machines but for some bizarre reason when I ran it on my VS it never did.
One thought that came to mind is that by VS uses the cassini default lightweight webserver for debugging, whereas my co-worker is using IIS.
This seems to suggest then that the ASP Development server does not support JQuery. Is this true and if not, what could the problem be?