UKoom » .NET http://www.ukoom.com Documentum, SharePoint, Alfresco, ECM... Tue, 25 Oct 2011 15:11:22 +0000 en hourly 1 http://wordpress.org/?v=3.2.1 Navigate Code and Text in Virtual Studio 2010 http://www.ukoom.com/navigate-code-and-text-in-virtual-studio-2010.htm http://www.ukoom.com/navigate-code-and-text-in-virtual-studio-2010.htm#comments Mon, 11 Apr 2011 18:28:47 +0000 ukoom http://www.ukoom.com/?p=1249 Original article: http://msdn.microsoft.com/en-us/library/9w13x3hh.aspx

There are various ways to move through text or code in the Code Editor using the mouse and navigation keys:

  • Use the arrow keys to move one character at a time, or the arrow keys in combination with the CTRL key to move one word at a time. Arrow keys move one line at a time also.
  • Click a location with the mouse.
  • Use the scroll bars or scroll wheel on the mouse to move through the text.
  • Use the HOME, END, PAGEUP, and PAGEDOWN keys.
  • Use CTRL+PAGE UP and CTRL+PAGE DOWN to move the insertion point to the top or bottom of the window, respectively.
  • Use CTRL+HOME and CTRL+END to move the insertion point to the start or end of the file, respectively.
  • Use CTRL+UP ARROW and CTRL+DOWN ARROW to scroll the view without moving the insertion point.
  • Use the Navigate Backward button to move the insertion point to previous locations in the active document, and the Navigate Forward button to return to more recent locations.

Operations such as Incremental Search, Goto Line, Goto Definition, Beginning of Document, End of Document, Paste, and Insert File can move the insertion point a significant distance within the active document. The Navigate Backward and Navigate Forward buttons retain the last 20 locations of the insertion point.

The following sections describe other ways to move to specific sections and lines of code:

  • Navigation bar
  • Bookmarks in the Bookmarks Window
  • Comment tasks in the Task List
  • Incremental searches
  • Go to Line command
  • Go to Definition command
]]> http://www.ukoom.com/navigate-code-and-text-in-virtual-studio-2010.htm/feed 0 Display Line Numbers in Virtual Studio 2010 http://www.ukoom.com/display-line-numbers-in-virtual-studio-2010.htm http://www.ukoom.com/display-line-numbers-in-virtual-studio-2010.htm#comments Mon, 11 Apr 2011 18:26:33 +0000 ukoom http://www.ukoom.com/?p=1247 ine numbers are not added to your code; they are for reference only. For line numbers to print, you must select Include line numbers in the Print dialog box. For more information, see How to: Print Code in the Editor.

To display line numbers in code

  1. On the Tools menu, select Options.
  2. In the categories list on the left side of the Options window, expand the Text Editor node.
  3. Expand the All Languages subnode and select General to set this option globally.
Note Note
Visual C# Express user must click Show All Settings to reveal the All Languages subfolder.

—or—

Choose the General options in the subfolder for the language in which you are programming.

  1. In the Display section select Line numbers.
]]> http://www.ukoom.com/display-line-numbers-in-virtual-studio-2010.htm/feed 0 Virtual Studio 2010 disable the automated TFS connection http://www.ukoom.com/virtual-studio-2010-disable-the-automated-tfs-connection.htm http://www.ukoom.com/virtual-studio-2010-disable-the-automated-tfs-connection.htm#comments Tue, 22 Mar 2011 16:29:08 +0000 ukoom http://www.ukoom.com/?p=1178 Add a DWORD value called “AutoLoadServer” under HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\TeamFoundation.

Zero means do not reconnect automatically.

]]> http://www.ukoom.com/virtual-studio-2010-disable-the-automated-tfs-connection.htm/feed 0 VB.NET to C# http://www.ukoom.com/vb-net-to-c.htm http://www.ukoom.com/vb-net-to-c.htm#comments Thu, 02 Sep 2010 11:53:08 +0000 ukoom http://www.ukoom.com/?p=1120 I came across this syntax error – “Non-invocable member ‘System.Windows.Forms.Control.Controls’ cannot be used like a method” when converting a VB.NET project to C#  windows form application.
In C#, weshould use bracket(“[", "]“) to retrieve item from a collection instead of using the parenthesis as in VB.NET.
VB.NET ->TabControl1.Controls(1).Enabled = False
C#         -> this.TabControl1.Controls[1].Enabled = false;

Issue – “Operator ‘==’ cannot be applied to operands of type ‘method group’ and ‘System.Windows.Forms.DialogResult’”
if (SaveFileDialog1.ShowDialog == System.Windows.Forms.DialogResult.OK)
It is calling the ShowDIalog method not the value of the dialog
if (SaveFileDialog1.ShowDialog() == System.Windows.Forms.DialogResult.OK)

]]> http://www.ukoom.com/vb-net-to-c.htm/feed 0 VS 2008 users: remember to download the SourceSafe CTP http://www.ukoom.com/vs-2008-users-remember-to-download-the-sourcesafe-ctp.htm http://www.ukoom.com/vs-2008-users-remember-to-download-the-sourcesafe-ctp.htm#comments Mon, 21 Dec 2009 07:45:07 +0000 ukoom http://www.ukoom.com/?p=986 You’ve probably all seen Soma’s announcement that the 2008 suite of products officially shipped this morning.  Good luck downloading — our servers are pegged :)

If you plan to use VS 2008 with SourceSafe, make sure to pick up the Update CTP too.  Without it, some features like “Open from Source Control” will not work at all.  Pay close attention to the install instructions as well.  As it says in the KB article:

You may receive error messages when you use Visual Studio 2008. This problem occurs because some compatibility fixes require the Tdnamespaceextension.dll file to be reregistered after you install Visual Studio 2008. To reregister the Tdnamespaceextension.dll file, type the following command at the [elevated - RB] command prompt:

regsvr32 “%programfiles%\Microsoft Visual SourceSafe\tdnamespaceextension.dll”

Sorry about the manual install step.  It sucks, I know.  The next Update won’t have this requirement.  (We wanted to ship it before Orcas but ran into some last-minute delays.  Expect it before the end of the year.)

Why does SourceSafe need an update anyway?  Aren’t VS plugin interfaces supposed to be backwards compatible?  Yes, they are.  In fact, there are no changes to the MSSCCI API in 2008; none of the fixes are related to MSSCCI.  (3rd party source control developers can now breathe a sigh of relief).  The changes come from the way SourceSafe implements Open from Source Control, Add to Source Control, and Share inside Visual Studio.

Starting in VSS 2005, these functions let you browse the database inside VS’s open/add dialogs instead of hanging off the File -> Source Control menu like most other source control providers.  It’s a cool trick known as a namespace extension.  In VS 2008, as you may have noticed, those open/add dialogs got a facelift: like VSS 2005, VS 2008 now uses the standard Windows dialogs.  So Vista users in particular get a spiffy new one with integrated search & everything.  Unfortunately, that change broke us pretty badly, leading in one way or another to at least 10 of the bugs on my list.  Bottom line, you don’t want to be caught without the Update linked above.

Hopefully these fixes demonstrate our commitment to keep SourceSafe 2005 a viable option with VS 2008, Vista, and beyond!

This article is from http://blogs.msdn.com/richardb

]]> http://www.ukoom.com/vs-2008-users-remember-to-download-the-sourcesafe-ctp.htm/feed 0 Visual Source Safe 2005 Update CTP VS80-KB939808-X86-ENU.exe http://www.ukoom.com/visual-source-safe-2005-update-ctp-vs80-kb939808-x86-enu-exe.htm http://www.ukoom.com/visual-source-safe-2005-update-ctp-vs80-kb939808-x86-enu-exe.htm#comments Mon, 21 Dec 2009 07:43:17 +0000 ukoom http://www.ukoom.com/?p=984 Fixes in the GDR include stability, performance, data integrity, and usability enhancements in many areas of the product.
It also improves compatibility with Visual Studio 2008 and Windows Vista™. A comprehensive list of fixes that were previously published in the Microsoft Knowledgebase can be found by following the appropriate link under Additional Information on this page.

System Requirements

  • Supported Operating Systems: Windows 2000 Service Pack 4; Windows Server 2003 Service Pack 2; Windows Server 2003 Service Pack 2 x64 Edition; Windows Vista Business; Windows Vista Business 64-bit edition; Windows Vista Enterprise; Windows Vista Enterprise 64-bit edition; Windows Vista Home Basic; Windows Vista Home Basic 64-bit edition; Windows Vista Home Premium; Windows Vista Home Premium 64-bit edition; Windows Vista Starter; Windows Vista Ultimate; Windows Vista Ultimate 64-bit edition; Windows XP Service Pack 2
  • Required Software: Visual Source Safe 2005

Instructions

This GDR prerelease may be installed before or after installing Visual Studio.
It is recommended that this GDR prerelease be installed before using SourceSafe integration inside Visual Studio 2008 (formerly codenamed “Orcas”). If you install Orcas, you must then reregister tdnamespaceextension.dll. Once fully installed, this GDR is compatible with all Orcas releases Beta 1 and later.

The GDR prerelease only needs to be installed once.

The GDR prerelease can be installed over any existing SourceSafe 2005 hotfixes. In addition, future hotfixes will contain all of the changes from this GDR (cumulative). Older builds will never overwrite newer builds.

It is recommended that you backup your SourceSafe databases before installing this GDR prerelease

To install this update, we recommend that you follow these steps:

  1. Save the download package on your computer.
  2. Double-click the download package to run the installer.

]]> http://www.ukoom.com/visual-source-safe-2005-update-ctp-vs80-kb939808-x86-enu-exe.htm/feed 2 Visual SourceSafe 2005 Update VS80-KB943847-X86-INTL.exe http://www.ukoom.com/visual-sourcesafe-2005-update-vs80-kb943847-x86-intl-exe.htm http://www.ukoom.com/visual-sourcesafe-2005-update-vs80-kb943847-x86-intl-exe.htm#comments Mon, 21 Dec 2009 07:15:25 +0000 ukoom http://www.ukoom.com/?p=978 This update is a rollup of bug fixes for Visual Source Safe. The fixed bugs include stability, performance, data integrity, and usability enhancements in many areas of the product. It also improves compatibility with Visual Studio 2008 and Windows Vista™. A comprehensive list of fixes is publsihed in the Microsoft Knowledgebase Article. The article can be found by following the appropriate link under Additional Information on this page.

  • This update may be installed before or after installing Visual Studio.
  • It is recommended that this update be installed before using SourceSafe inside Visual Studio 2008 (formerly codenamed “Orcas”). Once installed, SourceSafe 2005 is compatible with all Orcas releases.
  • The update only needs to be installed once.
  • The update can be installed over any existing SourceSafe 2005 hotfixes. In addition, future hotfixes will contain all of the changes from this update (cumulative). Older builds will never overwrite newer builds.
  • It is recommended that you backup your SourceSafe databases before installing this update.
]]> http://www.ukoom.com/visual-sourcesafe-2005-update-vs80-kb943847-x86-intl-exe.htm/feed 0 XSLT Study http://www.ukoom.com/xslt-study.htm http://www.ukoom.com/xslt-study.htm#comments Fri, 06 Feb 2009 09:36:00 +0000 ukoom http://www.ukoom.com/?p=509 Reference:

http://www.xslt.org.cn/books/xslt/index.htm

http://www.xml.com/pub/a/2001/05/07/xsltmath.html

http://www.xml.com/pub/a/2002/06/26/q-a.html

http://blog.csdn.net/cds27/archive/2006/05/21/747283.aspx

http://www.cnblogs.com/cime63/archive/2007/09/28/908754.html

http://stackoverflow.com/questions/231373/xslt-ie6-default-processor

http://shiningwu.javaeye.com/blog/152823

http://shiningwu.javaeye.com/blog/154361

]]> http://www.ukoom.com/xslt-study.htm/feed 0 Excel Financial functions for .NET http://www.ukoom.com/excel-financial-functions-for-net.htm http://www.ukoom.com/excel-financial-functions-for-net.htm#comments Mon, 29 Dec 2008 05:58:39 +0000 ukoom http://www.ukoom.com/?p=345 Considering that the .NET framework is easily on the short list for the most popular business application platform, it is surprising that financial functions are largely ignored. Sure there is a handful of methods squirreled away in VisualBasic.Financial, but most developers don’t even think to look there. It is no wonder companies often turn to Excel.

Excel Financial functions for .NET  is a .NET library that provides the full set of financial functions from Excel. The main goal for the library is compatibility with Excel, by providing the same functions, with the same behaviour. Note though that this is not a wrapper over the Excel library; the functions have been re-implemented in managed code so that you do not need to have Excel installed to use this library.

References:

http://www.infoq.com/news/2008/12/FSharp-Financial

http://code.msdn.microsoft.com/FinancialFunctions

]]> http://www.ukoom.com/excel-financial-functions-for-net.htm/feed 0 Versions of .NET Framework and Visual studio http://www.ukoom.com/versions-of-net-framework-and-visual-studio.htm http://www.ukoom.com/versions-of-net-framework-and-visual-studio.htm#comments Mon, 29 Dec 2008 05:47:03 +0000 ukoom http://www.ukoom.com/?p=339

Published: November 20, 2007 – 08:46AM CT

As promised earlier this month, Microsoft announced today that both Visual Studio 2008 and the accompanying .NET Framework 3.5 have been released to manufacture (RTM).

Codenamed Orcas, Visual Studio 2008 (VS2008) comes two years after Visual Studio 2005. In total, there are more than 250 new features added with significant enhancements across every version ranging from Express Editions to Visual Studio Team Systems (VSTS). A key addition in VS2008 is support for the new Language Integrated Query (LINQ), which is positioned as a technology for rapid application development. LINQ is designed to let developers focus on what they need the data to do, rather than be mired in the complexities of data abstraction and casting. Also, LINQ makes it easier to tie C# or Visual Basic with SQL.

In addition, VS2008 features multi-targeting support. Scott Guthrie, a general manager in the Microsoft Developer Division, explains in a blog post:

VS 2008 enables you to build applications that target multiple versions of the .Net Framework. This means you can use VS 2008 to open, edit and build existing .NET 2.0 and ASP.NET 2.0 applications (including ASP.NET 2.0 applications using ASP.NET AJAX 1.0), and continue to deploy these application on .NET 2.0 machines.

The .NET Framework 3.5 features enhancements to a number of built-in libraries as well as deliver a host of features relevant to Web 2.0, Service-Oriented Architecture (SOA) and Software plus Services-based applications.

Even though the product’s formal launch will not take place until next year, MSDN subscribers can download VS2008 and .NET Framework 3.5 here.

]]> http://www.ukoom.com/versions-of-net-framework-and-visual-studio.htm/feed 0