roudrigo

ESL - Closing email phrases

2010-06-24T13:46:00.001-03:00

I look forward to your reply.
I look forward to seeing you.
I look forward to hearing from you.
I look forward to hearing from you soon.
I look forward to meeting you next Tuesday.
I look forward to seeing you next Thursday.
We look forward to welcoming you as our customer.
I look forward to an opportunity to speak with you personally.
I look forward to a successful working relationship in the future.
I hope to get answers from you.
Good luck and I look forward to your response!
If you require any further information, feel free to contact me.
If you have any questions, please don't hesitate to contact us.
Should you need any further information, please do not hesitate to contact me.
I would appreciate your immediate attention to this matter.
Your prompt reply is very much appreciated.
Please contact us again if we can help in any way.
Please contact us again if there are any problems.
Please contact us again if you have any questions.
If you have any questions or concerns, please feel free to contact me.
If you have any question please contact us anytime and we will get back to you within 3 business days.
Let me know at your earliest convenience.
Please cascade this information as necessary.
Thank you buddy for considering...

ESL - Opening email phrases

2010-06-24T13:45:00.001-03:00

I am writing to confirm ...
I am writing to apologize for ...
I am writing to enquire about ...
I am writing to you in response to your advertisement for...
I received your address from + and would like ...
I recently wrote to you about ...
In reply to your letter of 8 May, ...
With reference to your letter of 8 June, I ...
With reference to your advertisement in ...
With reference to your phone call today, ...
After having seen your advertisement in ... , I would like ...
After having received your address from ... , I ...
Thank you for your letter of 8 May.
Thank you for your letter regarding ...
Thank you for your letter/e-mail about ...
To Whom It May Concern:
An update on this issue
More progress on this issue

Batch File - Converting a unix file to windows file

2010-06-08T15:03:00.002-03:00

TYPE unix_file.txt | FIND "" /V > windows_file.txt

or

FOR /f "eol= tokens=* delims=" %%i in (unix_file.txt) do echo %%i >>windows_file.txt

Batch File - Comparing dates of two files

2010-06-02T11:10:00.004-03:00

dir /b /OD file1.txt file2.txt | more +1

This only works if the files are in the same folder, and neither is hidden.
(Limitation of the Dir command)Compares Last Modified Date, but can easily
compare Created Date or Last Accessed Date using /TC or /TA.
To capture the filename in a batch file you can use a For loop:
Code:

For /F "Delims=" %%I In ('dir /b /OD file1.txt file2.txt ^| more +1') Do Set _Newer=%%I

You can use the /AH switch if both files are hidden, but it won't work if only
one is hidden. This will also do the same:
Code:

For /F "Skip=1 Delims=" %%I In ('dir /b /OD file1.txt file2.txt') Do Set _Newer=%%I

You can use Xcopy if the files are in the same or different folders, hidden or not,
but can only compare the Last Modified dates:
Code:

For /F "Delims=" %%I In ('xcopy /DHYL C:\Folder1\File1.txt D:\Backup\File2.txt ^|Findstr /I "File"') Do set /a _Newer=%%I 2>Nul

If File1 is newer, _Newer is set to 1. If same or older date, it's set to 0.
If you need the file name instead of a 1/0 answer, takes one more line:
Code:

For /F "Delims=" %%I In ('xcopy /DHYL C:\Folder1\File1.txt D:\Backup\File2.txt ^|Findstr /I "File"') Do set /a _Newer=%%I 2>Nul
If %_Newer==1 (Set _Newer=C:\Folder1\File1.txt) Else (Set _Newer=D:\Backup\File2.txt)

This will accept Fully qualified file names on the command line and output the
name of the newest file:
Code:

Set _File1=%1
Set _File2=%2
For /F "Delims=" %%I In ('xcopy /DHYL %_File1% %_File2% ^|Findstr /I "File"') Do set /a _Newer=%%I 2>Nul
If %_Newer%==1 (Set _Newer=%_File1%) Else (Set _Newer=%_File2%)
Echo The newest file is %_Newer%

If you need to compare the Created Date or Last Accessed Date for files in
different folders, you can move one of them, compare using the first option,
then move the file back. Not a good option for larger files, or files on a flash
drive. You'd have to parse the Date and time stamp from a Dir for each file,
convert it to a number format that batch can handle, and then compare
the timestamps. Doable, but much more involved using a batch file.
The GNU utilities would be much easier if you need to compare Created/Accessed
dates in different folders without moving either file. And it can do multiple
files, not just two

Batch File - Reading a flat file

2010-06-02T10:26:00.005-03:00

TEST.TXT:
indiana, brazil, 49
john, africa, 50
nicole, argentina, 13

----------------------------------------------------------------------------------------

FOR /f "delims=, tokens=1,2,3*" %%i in (C:\test.txt) DO call :read_file %%i %%j %%k
goto :END

:read_file
SET name=%1
SET country=%2
SET age=%3
ECHO %name%
ECHO %country%
ECHO %age%
goto :eof

:END
echo Execution Success!
exit 0

Batch File - Creating a log file with date/time

2010-06-02T10:06:00.005-03:00

FOR /F "tokens=2,3,4 delims=/ " %%I in ('DATE /T') DO SET LOGDATE=%%K%%I%%J
FOR /F "tokens=1,2 delims=: " %%I in ('TIME /T') DO SET TIMEVAR=%%I%%J

SET LOGFILE=D:\LOGS\logfile_%LOGDATE%_%TIMEVAR%.log

ESL - Connectors

2010-05-26T08:43:00.007-03:00

ADDITION:
and = e;
in addition = alem disso;
furthermore = alem disso;
besides = alem disso;
moreover = alem disso;
as well as = tambem, assim como, bem como;
also = tambem;
apart from = com exceção de;
both... and = ambos, tanto... como;
not only... but also = nao apenas... mas tb;
also.

CONTRAST, CONCESSION:
but = mas;
however = entretanto;
nevertheless = não obstante;
yet = entretanto, ainda;
nonetheless = não obstante;
despite that = apesar de;
in spite of = apesar de;
although = embora;
even thought = embora;
thought = embora;
raster than = em vez de;
instead of = em vez de;
Whereas, meanwhile = enquanto;
On the other hand.

PURPOSE:
in order to = a fim de;
so as so = de modo que.

CONSEQUENCE, CONCLUSION:
therefore = portanto;
consequently = consequentemente;
accordingly = de acordo;
fence = pois, entao, dai;
as a result = consequentemente;
thus = assim;
thereby = assim, desse modo;
so = entao, pois;
then = entao;
finally = finalmente
Otherwise= de resto;
In summary;
To sum up
To conclude;
In conclusion.

ALTERNATIVE:
otherwise = por outro lado;
or = ou;
or else = ou entao, ou ainda;
either... or = ou... ou;
whereas = enquanto;
while = enquanto;
whilst= enquanto.

CAUSE / REASON:
because = porque;
due to = devido a;
as = porque;
since = uma vez que;
In order to;
So as not to;
So that.

DOUBT OR HYPOTHESIS:
perhaps = talvez;
maybe = talvez;
possibly = possivelmente.

EMPHASIS:
that is = isto é;
in other words = em outras palavras;
in short = em resumo;
in brief = em resumo;
that is to say = quer dizer;
i. e. = isto é.

COMPARISON:
like = como;
than = do que;
as = como;
Likewise;
Similarly.

ILLUSTRATION:
e.g. = por exemplo;
for instance = por exemplo;
for example = por exemplo;
such as = tal como;
namely = a saber;
viz = quer dizer.

CONDITION:
if = se;
unless = se nao, a menos que;
provided that = uma vez que, se;
on condition that = desde que;
as long as = uma vez que;
subject to = sujeito a;
whether = e;
as = enquanto;
as = quando;
Otherwise.

Cross, Inner and Outer Join

2009-08-13T18:09:00.010-03:00

For you and me that always forget the differences between the ANSI and traditional join syntax, I wrote this quick guide. Let’s take a look.

The fundamental join types differ in the logical phases that they apply:

Cross join applies only the Cartesian product,
Inner join applies the Cartesian product and the ON filter,
Outer join applies Cartesian product, ON filter and add outer rows.

Cross Join
Performs a Cartesian product between two tables. In other words, it returns a row for each possible combination of a row from the left table and a row from the right table. If the left table has n rows and the right table has m rows, a cross join will return a table with n x m rows.

ANSI	Traditional
SELECT E1.FirstName, E1.LastName AS emp1,E2.FirstName, E2.LastName AS emp2 FROM dbo.Employees AS E1 CROSS JOIN dbo.Employees AS E2;	SELECT E1.FirstName, E1.LastName AS emp1,E2.FirstName, E2.LastName AS emp2 FROM dbo.Employees AS E1, dbo.Employees AS E2;

The optimizer will produce the same plan for both, so you shouldn't have any concerns about performance.

Inner Join
Applies the first and the second table (Cartesian product, ON filter)

ANSI	Traditional
SELECT C.CustomerID, CompanyName, OrderID FROM dbo.Customers AS C JOIN dbo.Orders AS O ON C.CustomerID = O.CustomerID WHERE Country = 'USA';	SELECT C.CustomerID, CompanyName, OrderID FROM dbo.Customers AS C, dbo.Orders AS O WHERE C.CustomerID = O.CustomerID AND Country = 'USA';

Outer Join
Outer joins are used to return matching rows from both tables based on some criterion, plus rows from the "preserved" table or tables for which there was no match. You identify preserved tables with the LEFT, RIGHT, or FULL keywords. LEFT marks the left table as preserved, RIGHT marks the right table, and FULL marks both.

SELECT C.CustomerID, CompanyName, OrderID
FROM dbo.Customers AS C
LEFT OUTER JOIN dbo.Orders AS O
ON C.CustomerID = O.CustomerID;

That's just SQL, but I like it.

Querying...

2009-08-13T13:33:00.002-03:00

One of most important things that you have to know about writing optimized queries in SQL Server is the sequence of each clause is executed.

(8) SELECT (9) DISTINCT (11)
(1) FROM
(3) JOIN
(2) ON
(4) WHERE
(5) GROUP BY
(6) WITH {CUBE | ROLLUP}
(7) HAVING
(10) ORDER BY

Each step generates a virtual table that is used as the input to the following step. These virtual tables are not available to the caller. Only the table generated by the final step is returned to the caller. If a certain clause is not specified in a query, the corresponding step is simply skipped. See a little bit explanation about logical query processing:

1. FROM: A Cartesian product (cross join) is performed between the first two tables in the FROM clause, and as a result, virtual table VT1 is generated.

2. ON: The ON filter is applied to VT1. Only rows for which the is TRUE are inserted to VT2.

3. OUTER (join): If an OUTER JOIN is specified (as opposed to a CROSS JOIN or an INNER JOIN), rows from the preserved table or tables for which a match was not found are added to the rows from VT2 as outer rows, generating VT3. If more than two tables appear in the FROM clause, steps 1 through 3 are applied repeatedly between the result of the last join and the next table in the FROM clause until all tables are processed.

4. WHERE: The WHERE filter is applied to VT3. Only rows for which the is TRUE are inserted to VT4.

5. GROUP BY: The rows from VT4 are arranged in groups based on the column list specified in the GROUP BY clause. VT5 is generated.

6. CUBE | ROLLUP: Supergroups (groups of groups) are added to the rows from VT5, generating VT6.

7. HAVING: The HAVING filter is applied to VT6. Only groups for which the is TRUE are inserted to VT7.

8. SELECT: The SELECT list is processed, generating VT8.

9. DISTINCT: Duplicate rows are removed from VT8. VT9 is generated.

10. ORDER BY: The rows from VT9 are sorted according to the column list specified in the ORDER BY clause. A cursor is generated (VC10).

11. TOP: The specified number or percentage of rows is selected from the beginning of VC10. Table VT11 is generated and returned to the caller.

I hope this helps. Thanks!

Visual Studio Shuts Down Suddenly

2009-08-12T22:40:00.002-03:00

Sunny day in my city and I’m developing a simple application by using ASP.NET MVC 1.0 on my Visual Studio 2008 SP1 – I’ll write about that soon. After writing some lines of code, I try to open a .aspx file when my Visual Studio shuts down suddenly. Hmmm… I open Visual Studio again, open my project as well and try to open another .aspx file… Visual Studio shuts down again! Again! And Again! What’s going on? I ask myself. What’s the problem with .aspx files?

In Event Viewer, I found the possible error related with that:

.NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (7A035E00) (80131506)

So I ask the buddy Google about that. I found that this issue can be related to PowerCommand that was not compatible with newer assemblies version in SP1.

I uninstalled the PowerCommand from my machine and my Visual Studio doesn't shut down anymore… Now I can edit my .aspx file.