View Complete Post
I've look around the forums but I can't get the solution for my problem. I've installed Visual studio 2010 with sqlexpress edition. Then I have renamed my
computer. After renaming my computer I've deleted the directory
C:\Users\uporabnik\AppData\Local\Microsoft\Microsoft SQL Server
Data\SQLEXPRESS. After restart, I have started VS2010, open Server explorer and I've added the connection to a new database. I've been able to add new tabels, bu when I've tried to add a diagram, it didn't work. In properties window od the database I
saw, the the database owner was oldComputerName\username not newComputerName\userName. In
sql server management studio I've reanmed the user oldComputerName\userName to newComputerName\userName. After attaching the database it worked fine.
I've returned to Visual studio 2010. When creating new database, the owner of new database is oldComputerName\userName. The next tip was renaming the SQLServerMSSQLUser$ComputerName$SQLEXPRESS(and other names with sql...) in
Local Users and gorups in Mange My computer. After restarting the compter I've got the same result. When creating new .mdf file in server explorer of visual studio, the database owner is oldComputerName\userName.<
I'm new to HttpHandlers. I am writing an HttpHandler that reads uploaded files directly from the request stream to provide progress that can be queried using an AJAX request. For large files, this seems to be faster than having ASP.NET load the file contents into Request.Files and then streaming the file from there to wherever it goes (Linq to SQL into a VARBINARY column in an SQL Server database.)
My HttpHandler works perfectly when I'm debugging using the Visual Studio Development Server, but doesn't work otherwise. The application pool for this application in IIS 7 is set to run in Classic Mode, and the Handler Mappings screen in IIS says that I must manage managed handlers in system.web/httpHandlers.
I set up in my applications Web.config file.
<add verb="GET,POST" path="*.upload" type="Namespace.For.UploadHandler, AssemblyForUploadHandler"/>
It works great, so long as I don't debug with the "Use Local IIS Web server" option.
What else do I need to do to get this to work?
There's no magic behind how the TFS Power Tools were integrated with Team Explorer, and we'll show you how to expose your own custom features inside the Team Explorer window.
Brian A. Randell, Marcel de Vries
MSDN Magazine December 2009
The latest releases of WinDBG and Visual Studio know exactly how to use source server, so its benefits are available to both .NET and native C++ developers. See why this is so important in tracking down bugs.
MSDN Magazine August 2006
When developing high-performance applications for the Web, developers often must choose between performance and ease of development. With ATL Server, new with Visual Studio .NET, developers get the best of both worlds. ATL Server uses a tag replacement engine written in C++, provides a simple programming model, and promotes enhanced performance and easy debugging. This article presents an overview of the ATL Server architecture, then creates a basic ATL Server project. It then goes on to explain processing SRF files, HTTP streams, forms, cookies, and header files. Managing session state is also discussed, along with file uploads and performance monitoring.
Shaun McAravey and Ben Hickman
MSDN Magazine October 2000