ATTENTION: I've decided to put the upgrade on hold due to a compatibility issue of our server environment with the latest CS installer package. CS 2008 now requires SQL Server 2005 as the backend DB but our database server currenlty has SQL Server 2000 installed on it. I'll resume the upgrade once I figure out when Telligent is releasing a patch to the schema compatibility issue. For now, we will continue to use the old version of CS while waiting for the said patch. If you have any questions about this process, please don't hesitate to post them on our forums and I'll answer them as soon as I can. Thanks for your patience and support guys! I'll let you know as soon as this is resolved. -
Keith Rull
Browse Site by Tags
Showing related tags and posts accross the entire site.
All Tags »
visual studio »
tips »
.NET (RSS)
-
i noticed yesterday that my double quote key is switched with the @ key in visual studio. i tried it in notepad and it seems to be working. i'm glad i found a helpful post in the msdn forums this morning on how to fix this and it turns out that i have two language settings installed, US and UK, i...
-
the development machine of my teammate is pretty messed up so i assumed that the hooking up of visual studio ide events on his machine is not working. one of the features i love with visual studio is when it automatically highlights the currently active code sheet in the solution explorer and this feature...
-
I wanted to browse the tables of a Microsoft Access mdb file but unluckily, i just have the standard edition of Microsoft Office on my machine (which obviously does not have Microsoft Access). Obviously it's not a problem for me, since I have Visual Studio installed. I just need to create a new data...
-
was reading some of my .NET feeds when i bumped into Roy's post on VS shortcuts Press Ctrl-X or Ctrl-C in a line where you have *no selection* - and you'll automatically copy or cut the entire current line. Save lots of time and pain, and just isn't well known. (why did i not know about that!) http:...
-
i am currently exploring log4net and how to use it to my newly assigned project. i downloaded the source code and i needed to install it in the gac so i can easily reference it in my projects. i tried to rebuild the source and had some problem with strong naming. couldn't figure out what the problem...
-
I always try to supply xml documentation for my codes no matter how descriptive I name my methods and properties. I wanted my team to take advantage of the xml comments that I have provided through Intellisense for some of the classes that I have done and revised so I configured our solutions to produce...
-
I always use the collapse to definitions/toggle all outlining feature of VS editor. I have long wanted to be able to do the same with solution explorer and this afternoon, I was able to find a macro just for the collapse all through usenet. http://www.codeproject.com/macro/collapseall.asp
-
I think the most common mistake that I always encounter with VS is on adding new projects. I have all the VS family installed (VB.NET, C#, etc.) and I sometimes use VB.NET just for trying some things out. When I want to add a new C# Console Project, I quickly browse to the Console Application Template...
-
When you just want to watch for the result of a particular operation, like (this.Right - this.Left)/2 you don't need to copy and paste it in the Immediate Window or launch QuickWatch with the expression selected. You just have to select the said expression and point the mouse over it.
-
You want to debug your source code in VS but then the breakpoint that you set has a question mark in it saying "Breakpoint will not be hit." I have two reasons that I can provide you: Debug symbols are not loaded The assembly being used is a different version / assembly is not yet loaded This is where...