MSDN Magazine October 2004
View Complete Post
I believe this issue got by so many people already.
We have a sharepoint site running on HTTPS protocol. There are some scenarios we get multiple documents from customers and need to move them to SharePoint to share them across organization. For this, what we are doing is, we are opening the library and from
Actions menu -> Open in Windows Explorer.
The windows explorer is opening fine and when we tried to move the files from local system to windows explorer of the SharePoint site, it is failing to copy data and showing 0KB moved. And at the windows taskbar it is giving notification like "Got network
delayed write fail message." when we are doing this on XP. On any other OS, there is no notification and not moving the file.
We are not able to understand the problem. Why it is not able to move, everytime it is copying 0KB.
We can do using upload multiple files feature, but we have to go back and forth between folders and it will slow down the process.
Please help me out, why it is happening... It is not network issue at all for sure.
For uploading or copying large number of documents i can use windows explorer view in moss.
Is this view requires administrative permission.
Suppose i have a workflow for each document in the library,If i copy in bulk documents to the library.will the workflow be attached by default.
Hello i am a basic programmer in visual basic 2010.
every place you go they wrote how insert a text format between your project (first textbox to second textbox) but i cant find how insert files from out of your form into your form.
for example how i should get file paths by using drag drop.
i want insert several files (Rar) into my form in my listbox
anybody can help me
I have a Windows Forms sample app that we use to illustrate drag and drop functionality with our external application. The sample app contains two list boxes, a DragSource and a DropTarget. The DragSource is populated with data that can be dragged and dropped
to the DropTarget, or to our external application. The sample app is written in Visual Studio 2008 using a Windows Forms Application that links to a legacy C++ library.
1. Dragging and dropping between the two listboxes in the same instance
2. Dragging and dropping between the sample app and our external application
What doesn't work and hope to get your feedback on:
1. Dragging and dropping between the sample app and another instance of the sample app fails to read data from the MemoryStream and indicates the following exception: "A first chance exception of type 'System.Runtime.Remoting.RemotingException' occurred
2. Dragging from the DragSource indicates the following exceptions although the DropTarget and our external application are able to read the stream and display the information.
A first chance exception of type 'System.Runtime.InteropServices.COMException' occurred in System.Windows.Forms.dll; A first chance exception of
Jeff Prosise shows how you can implement drag-and-drop functionality in your Web app with ASP.NET AJAX.
MSDN Magazine January 2008
Why is a change to the Windows logon plug-in interface so exciting? Because with credential providers you can customize the logon experience for your users.
MSDN Magazine January 2007
Extending the Windows shell with namespace extensions allows you to create some custom functionality for Windows Explorer. One common use is to enable Explorer to present a list of items that do not exist in one real folder, but actually reside in a number of places. The view on the folder makes it look like these items are in one place, so managing them becomes easier. This article illustrates the process of creating custom shell namespace extensions using C# and the .NET Framework. The author dispels some myths about the difficulty of writing such extensions, and shows that it is easier than it was before .NET. Along the way he outlines undocumented interfaces and describes advanced techniques for consuming them in .NET.
MSDN Magazine January 2004
LinkLabels are Windows Forms controls that enable a user to hyperlink to a URL that points to either the Web or the local directory system. While the SDK documentation discusses the control, it does not demonstrate how linking is accomplished, nor does it outline the power and flexibility the control provides. This article fills those gaps, showing how to link using the LinkLabel control. It also shows the flexibility of this control for the programmer using the .NET Framework. In addition, the author covers the large number of properties that allow you to customize your controls and accurately place them. Their built-in behaviors are also discussed, along with their use in both Visual Basic .NET and C#.
MSDN Magazine February 2003
DirectShow is an API that enables Windows applications to control a wide variety of audio/video input devices including (but not limited to) DV camcorders, Web cams, DVD drives, and TV tuner cards. It provides out-of-the-box support for a variety of formats, from WAV and AVI to Windows Media. DirectShow is also extensible, enabling third parties to support their own specialized devices, formats, or processing components. This article introduces the basic concepts behind DirectShow and gives a step-by-step tutorial showing how to create your own video effect filter.
Michael Blome and Mike Wasson
MSDN Magazine July 2002
Windows Forms applications solve many of the problems inherent in building Web applications the old fashioned way?with HTML. To demonstrate the use of Windows Forms over the Web, the author takes his existing app, Wahoo!, and ports it to Windows Forms. In doing so, he discusses versioning, linked files, security, storage isolation, the deployment model, and everything else you need to get started building your own Windows Forms apps for the Web.
The Windows XP kernel includes a number of improvements over Windows 2000 that promote better scalability and overall performance. This article covers these changes and explains how they improve startup time, increase registry size limits, and promote more efficient disk partitioning. Windows XP provides support for 64-bit processors, which is covered here along with a discussion of how side-by-side assemblies end DLL Hell. Also new in the Windows XP kernel is a facility that will roll back driver installations to the Last Known Good state of the registry, making driver installation safer. Other topics include the new volume shadow copy facility, which provides for more accurate backups and improvements in remote debugging.
Mark Russinovich and David Solomon
MSDN Magazine December 2001
Windows Management Instrumentation (WMI) is based on an industry-wide standard for notifications used to manage objects and devices across a network. By receiving WMI events, an application can be notified of changes to data in WMI itself. This allows the developer to notify the consuming application that certain system configuration data has changed, without the application having to poll WMI continuously for this data. The author presents an explanation of the different types of events in WMI, then goes on to develop an event provider.
J. Andrew Schafer
MSDN Magazine September 2001
The Internet provides the infrastructure for applications to communicate, and that can include non-UI communication between Win32-based applications. If you think beyond the standard browser usage of HTTP, you can use this protocol to retrieve information from Win32-based applications and save it to a Web server. After explaining how HTTP can be used in this way, this article shows how to use Microsoft SQL Server, ASP, IIS, WinInet, and Visual Basic to implement two examples. The first reports usage data-how often an application is used and by whom. The second monitors application errors and reports error details for use by helpdesk staff or engineers in the debugging process.
MSDN Magazine June 2001
Web Forms have the potential to change Web programming by introducing a new programming model built around server-side controls-a model in which controls render their own UIs by generating HTML to return to clients and firing events that are handled by server-side scripts. Since all the action takes place on the Web server, virtually any browser can run a Web Forms app. And thanks to Visual Studio .NET, building a Web Forms app is a lot like using Visual Basic: just drop a control onto a form then write an event handler. This article describes the Web Forms programming model, how it fits with ASP.NET, and introduces DataGrid, TextBox, and other classes in the .NET Framework class library.
MSDN Magazine May 2001