Autocomplete and IntelliSense
If you’ve been developing programs for a while, you probably either love autocompletion features or you hate them. If you’re in the former camp, or you’re just getting started with programming, this tip is just for you. Autocomplete, or the Microsoft equivalent, IntelliSense, is a feature within certain software that tries to automatically complete what you’ve started typing before you finish typing all of the letters yourself. For a lot of people, this is a real time-saver and can prevent typographical mistakes. But what if you’re working on code in a text file, or in a development environment that doesn’t have autocomplete? Here are a few utilities that can help you out. Continue Reading
Many developers struggle with the use of 32-bit and 64-bit address spaces. In a nutshell, 32-bit assemblies cannot be loaded within 64-bit address spaces and 64-bit assemblies cannot be loaded within 32-bit address spaces. Web applications are no different. As a result, special attention needs to be paid to the requirements of web applications running on 64-bit servers. 
The Visual Studio Integrated Design Environment (IDE) is highly customizable and can be extended. In fact, it’s possible to automate repetitive and tedious item creation tasks through the use of Item Templates. Consider the insertion of a copyright as the first line in all new class files. Under normal circumstances, this would be a manual task with each new class file created, but Item Templates can automate the process. The steps below outline the procedure for accomplishing just that using Visual Studio 2005. 
Global collaboration can be tricky for a number of reasons. For instance, when developing an application that is shared between users in two or more time zones, an important item to consider is the accuracy of time and date calculations. When making decisions based on dates and times, differences in time zones can substantially affect the integrity of data. This article describes some practices meant to limit your risk. 
The SolidWorks API (Application Programming Interface) is immensely powerful. In fact, if something is doable within SolidWorks, the chances are good that there is a corresponding API. As a result, automation possibilities are endless. The SolidWorks API documentation is outstanding and, in most cases, provides exceptional detail. However, one area that is somewhat tricky to navigate is event handling. This article will cover an example for event handling when developing for SolidWorks. 
When planning any software development project, whether it is a point or enterprise solution, there are several key questions to answer before a line of code is written. How will you know it’ll work on the required operating systems? How can you give the developers a standard development environment without buying or configuring hardware? Once developed, how can it be tested? Virtualization is a simple yet effective way for addressing these critical concerns related to software development environments. 
With every upgrade to ENOVIA SmarTeam (not to mention upgrades to CAD, Office and database platforms) there’s no question about the 
