I honestly don't understand why they thought it was a great UX to persistently show "sign up" page instead of "sign in" page. Odds are that I'm already registered so why are they making me clicking one more time just to get to sign in?
I need some help pond. Have a sunk to a new low or reached a new high of Excel abuse. 'Cause y'know 160MB workbooks be a thing I'm forced to do right now.
TLDR = No db and we need 11,000,000 results from a parametric sweep. Solution: Build a DB? Hells no, ain't got time for that. Split them up into groups of 500,000 rows each! That fixes the problem.
I recently posted this question on my implementation of an ADODB Wrapper Class. I realized in my own review that I was missing some very important things, so much so, that I decided it would be worth it to re-write the entire class. Saying that I have done quite a bit of restructuring so I am goi...
So, question, should i do var Connection = new System.Data.SqlClient.SqlConnection(); or System.Data.SqlClient.SqlConnection Connection = new System.Data.SqlClient.SqlConnection();
As an attempt to learn multithreading better, I wrote a program to crack the password of a ZIP file. It is sort of slow, processing a three-digit password of the 95 printable ASCII characters in about 1:45 minutes. This is my class that actually handles the cracking:
class DecryptPassword
{
...
Is there anything on SO that will show you the last 10, 20, 50 questions you visited? I just closed a tab earlier today then deleted stuff that that question documented. :/
How can I programatically (C#) ZIP a file (in Windows) without using
any third party libraries?
If using the 4.5+ Framework, there is now the ZipArchive and ZipFile classes.
using (ZipArchive zip = ZipFile.Open("test.zip", ZipArchiveMode.Create))
{
zip.CreateEntryFromFile(@"c:\somethi...
but 1.0 is only good on .NET FX 4.5 and I need it for 3.5
hmm. I probably should be re-leasing it as .NET standard. That means I don't need to have any computers to have a certain version of .NET FX installed... right?
uh. Your DB is in SQL Server. SSMS talks to it using native protocols (forgot the name ATM). ADO providers is for any other programs that needs to talk to the db. Two different categories.
TDS protocol is the name of SQL Server's native protocol I was trying to remember.
But the whole point of OLEDB or ODBC is that you get a common representation so that you can change database but still have same programming logic in your client code.
So VBA uses ADO to talk to the SQL Server db. Any communication within SSMS is native.
Yet again another layer on the abstraction lasagna so as to not worry about the implementation detail. Coding against the abstraction and not the concretion strikes again.