By -
WinForm applications StartUp Path:
No more talk, time has come now to code: let's start somewhere: anywhere in fact in this large world of multi - purpose development. Well I was working on an Office automation stuff. Having a word document repository folder in my .Net solution Folder let's say FolderA, and knowing that at execution time I'll be located into the FolderA\bin\Debug directory I supposed I could use something like @"..\..\doc" to get into the FolderA\docs directory. Why didn't it work ? I 'll know one day.But when your are coding on projects you don't have time to think a lot, you just have time to make things work as expected. So I didn't wait anymore : I used Application.StartupPath function, mixed it with something like Application.StartupPath.Substring(0, Application.StartupPath.Length-9) + "doc" and I could get the result.
I will come back later to my "Zen of code Optimisation" book and see if something there would help me fastening the code in this cow world of >2 Ghz speed processors

Comments

Post a Comment

Popular posts from this blog

By -
We are taking off for a new adventure in development: It's about developing a framework which will enable us to persist our business objects into databases, file systems or xml file system. STEP 1: CREATING A BUSINESSOBJECT ATTRIBUTE namespace ORMCore { /// /// This attribute is used to enable the ORMFramework /// to create an associate table on the RDBMS /// [ AttributeUsage(AttributeTargets.Class, AllowMultiple = false)] public class BusinessObjectAttribute:Attribute { private string _databaseName; public string DatabaseName { get { return _databaseName; } } private string _databaseConnexionString; public string DatabaseConnexionString { get { return _databaseConnexionString; } } public BusinessObjectAttribute(string databaseName) { this._databaseName = databaseName; } public B
Read more
By -
Image
Sql Server adapters for Biztalk Server One of the greatest difficulties I found when I started working with BizTalk 2004 was the lack of documentation about the SQL Adapter. In this article, I'm going to demonstrate how we can use this adapter in an Orchestration of BizTalk. The Example To build this example, we're going to use the Northwind database. We're going to simulate a hypothetical situation where we receive an XML message as a file, containing the order number, a customer ID, and the date of the order. In the orchestration, we will use SQL Server to search the additional information about the customer, using the SQL Adapter. Creating the Project We'll start this article by creating a new BizTalk Server project in Visual Studio. In the Visual Studio .NET menu, select the "New Project" option, and for the type of project, select "BizTalk Projects". Select the template "Empty BizTalk Project" and create a project named OrderManager.
Read more
By -
Writing effective adapters for Biztalk Server Introduction Many people, both within Microsoft and in third-party companies, have written successful adapters for Microsoft® BizTalk® Server. This task can be difficult, and this paper is intended to present some of the "tricks of the trade" that these developers have learned, in the hope that these will help others avoid common problems. This document is structured as a set of issues that programmers face when writing adapters, and provides guidelines for resolving these issues. These guidelines can be read in any order, although you may find that reading the whole document first will make the individual guidelines easier to understand. Effective Writing for Adapters Much of the complexity in writing adapters for BizTalk Server is centered on the problems of batched operations and that is what we will look at first. Operations, Messages, Batching, and Transactions Adapters commonly support sending messages to and receiving messa
Read more