|
|
How to Clean Word |
|
Word is a pack rat. If it doesn't close properly, or if you forget to do the voodoo dance of existential symmetric closure while creating your styles, or just use it how the average normal person would use it, Word will eventually have a problem due to its attic full of treasures. Here's how you clean Word out and reset it back to defaults!
|
 Read more...
|
|
Need some help in order to make decisions? |
|
Ever having trouble making decisions? Well now there is a solution in sight. Well at least to those that have connection to internet.
|
|
Read more...
|
|
Free Project/Time Management Tools |
|
I will admit it, I love the project management aspect of my job. I also love talking to customers and doing the actual work, the thought of trying to keep track of everything I am doing, need to do, and might need to do makes me a little bit nervous. Luckily, there are tools out there that can help make our management lives easier. The bad news however, is most of them are quite costly. Great, now we have to work more to pay for the tools that let us work more.
|
|
Read more...
|
|
.Net Dependencies tools |
|
Here are a couple of links about dependencies explorers, because some times you need to know on what your application relies:
|
|
Read more...
|
|
Introducing My Weekly Planner! |
|
For the last several months my productivity system (system is an ugly word right now but we all still need one) has revolved around two simple tools; a notepad and my weekly planner.
|
|
Read more...
|
|
(Interop)erability Performance |
|
With every transition from managed code to unmanaged code (and vice versa), there is some performance overhead. The amount of overhead depends on the types of parameters used. The CLR interop layer uses three levels of interop call optimization based on transition type and parameter types: just-in-time (JIT) inlining, compiled assembly stubs, and interpreted marshaling stubs (in order of fastest to slowest type of call).
|
|
Read more...
|
|
(Interop)erability Guidelines |
|
There are several types of unmanaged APIs and several types of interop technologies available for calling into them. Suggestions about how and when to use these technologies are described in here. Please note that these suggestions are very general and do not cover every scenario. You should evaluate your scenarios carefully and apply development practices and/or solutions that make sense for your scenario.
|
|
Read more...
|
|
Introduction to (Interop)erability |
|
The common language runtime (CLR) promotes the interaction of managed code with COM components, COM+ services, the Win32® API, and other types of unmanaged code. Data types, error-handling mechanisms, creation and destruction rules, and design guidelines vary between managed and unmanaged object models. To simplify interoperation between managed and unmanaged code and to ease the migration path, the CLR interop layer conceals the differences between these object models from both clients and servers.
|
|
Read more...
|
|
How to call C++ code from Managed, and vice versa (Interop) |
|
Interop - calling native (C++) code from managed (C#, VB, J#, MC++) and vice versa - can be very useful if you are trying to extend your libraries without porting existing code. However, it can often be confusing for a newbie to figure out how to set this up.
|
|
Read more...
|
|
Project Documentation Templates |
|
Here is the list of links that have helped me while writing Software Project Documentation.
|
|
Read more...
|
|
| 