WOW...Cool desktop blogging for weblogs.asp.net
ILMerge is a utility that can be used to merge multiple .NET assemblies into a single assembly. ILMerge takes a set of input assemblies and merges them into one target assembly. The first assembly in the list of input assemblies is the primary assembly. When the primary assembly is an executable, then the target assembly is created as an executable with the same entry point as the primary assembly. Also, if the primary assembly has a strong name, and a .snk file is provided, then the target assembly is re-signed with the specified key so that it also has a strong name.
ILMerge is packaged as a console application. But all of its functionality is also available programmatically. While Visual Studio does not allow one to add an executable as a reference, the C# compiler does, so you can write a C# client that uses ILMerge as a library.
There are several options that control the behavior of ILMerge. See the documentation that comes with the tool for details.
Currently, ILMerge does not work on Rotor or Mono.
For More ...
Good SQL Information
SQL Profiler - Template Trace
As a SQL programmers or DBA's many open and work with profiler as an extensive tool. But what we more often ignore is the standard templates that SQL Server provides with Profiler. This is a nice information to understand and use to make useful analysis out of our profiler traces.
SQL Script :
A very good resource for SQL Script.
Wha....This is what i was looking for long time ago.I always get a common question directly/indirectly which is somthing similar to below.Thanks to —J.T.
How does an average developer win fame and recognition as a guru on the programming scene?
To make a long story short, today there are literally millions of people who are targeting Windows when they sit down to code. Still, there's a lot of opportunity for widespread recognition. Every author in this magazine started small, with their first submission.
If you want to make a name for yourself in the world of programming, the first commandment is to know exactly what you're doing. Nothing will make people ignore you faster than if they can't trust your work. One thing you'll find in the community of programmers is that people can smell B.S. a mile away. Software itself is really nothing more than the end product of a bunch of thoughts put together, and if the software isn't sound, it's a sure sign that the underlying ideas aren't either.
The second commandment is to have an idea. This sounds simple, but it's the toughest thing to do. If you want to demonstrate a concept, it should be unique and it should fill a need. We see submissions all the time from people who want to show how to create a form or how to write a simple Web service—these ideas are well-trod by now.
Most great ideas are born of necessity. People have written RAW file viewers for their cameras, mobile blogging tools, and all sorts of power toys for Visual Studio. If you get something started, you don't even need to perfect it yourself; put it up in a shared workspace on gotdotnet.com or elsewhere, and invite others to add to the project you own.
The third commandment is that you must express yourself clearly, both through your writing and your code. A bad cover letter, with spelling and grammatical errors, severely limits an editor's confidence in the care you take in the rest of your work.
Finally, the fourth commandment is to keep your options open. A magazine is one place to get started, but if you join the expanding community of dev bloggers, you won't have to wait for acceptance before you start sharing your ideas.
Think of your favorite source of development information. Is it a magazine? A blog? A column? A book? A chat list? What do you get from this source that's unique? There's no need to reinvent the wheel when you're getting started. If you have something to share, do it through your favorite source. Even if you're not an MVP, you can offer your expertise, creativity, and guidance.
For More ...
You can debug SQL Server stored procedures, functions, and triggers in much the same way that you debug other kinds of scripts or programs from Visual Studio .Net IDE.
Note SQL debugging with Microsoft SQL Server 7.0 or SQL Server 2000 requires Visual Studio .NET Enterprise Developer or Visual Studio .NET Enterprise Architect Edition.
In This Section
- Debugging SQL Stored Procedures
- Provides instructions on debugging stored procedures from Server Explorer or from a source window.
- Debugging Extended Stored Procedures
- Defines an extended stored procedures and provides steps for debugging one.
- Walkthrough: Debugging Hello World, a SQL Stored Procedure
- Demonstrates how to debug stored procedures on a SQL Server. Information includes connecting to a database, creating a stored procedure, stepping into a stored procedure, setting breakpoints, viewing parameters and local variables in the Locals window, and dragging variables from the Text editor into the Watch window.
- SQL and Mixed-Language Debugging
- Describes debugging mixed-language applications, supported technologies, debugging remote applications, component requirements, enable SQL debugging, SQL debugging and running applications, and T-SQL and managed or unmanaged code.
- Monitoring the Flow of SQL Debugging Information
- Suggests using the Network Monitor (NetMon) or a similar tool to monitor the flow of SQL debugging information and provides a pointer to the Network Monitor documentation.
- SQL Debugging Limitations
- List the limitations that apply to debugging SQL source code.
- Setting Up SQL Debugging
- Lists software requirements for SQL debugging (for the server and workstation), instructions for enabling SQL debugging, installing, configuring, and troubleshooting setup.
- SQL Debugging Setup Errors and Troubleshooting
- List issues you may encounter when setting up SQL debugging and solutions to those problems.
- Overview of Visual Database Tools
- Describes Microsoft Visual Database Tools and provides links to: what's new in Visual Database Tools, Visual Database Tools components, work you can do with the Visual Database Tools, relationship between Visual Database Tools and databases, and database connections and references.
- Provides reference material for SQLExecDirect, which executes a preparable statement, using the current values of the parameter marker variables if any parameters exist in the statement. SQLExecDirect is the fastest way to submit an SQL statement for one-time execution.
- Provides reference material for SQLExecute, which executes a prepared statement, using the current values of the parameter marker variables if any parameter markers exist in the statement.
- System Stored Procedures
- List system stored procedures (Transact-SQL Reference).
- Debugging Home Page
- Provides links to the larger sections of the debugging documentation. Information includes what's new in the debugger, settings and preparation, breakpoints, handling exceptions, edit and continue, debugging managed code, debugging Visual C++ projects, debugging COM and ActiveX, debugging DLLs, debugging SQL, and the user interface references.
Troubleshooting tips for T-SQL Debugger in Visual Studio .NET
HOW TO: Debug Stored Procedures in Visual Studio .NET