|
A folder full of console applications for me. That's my usual .Net testing approach.
|
|
|
|
|
|
Haha, that folder name is called "POC" for me.
Been doing that from day 1 of my career.
|
|
|
|
|
The worst thing is when you *think* you have given it a descriptive name, but then a week later you have no idea what the hell it is 
|
|
|
|
|
Exactly!
|
|
|
|
|
I usually include a console app in my solutions called "TestHarness". That way, I can test right there in the same solution, and use all the assemblies referenced therein.
For casual stuff not directly associated with a project and that doesn't need a GUI, I use a console app.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Me too.
Sorry for my bad English
|
|
|
|
|
Ha, this reminds me of the HPCs I work with.
When I got here, they were developing a web service API for various things. Their strategy was to deploy to test, and hit the web service, then retrieve logs from the test server and plow through them looking for errors, and/or review the results in the app that worked those kinds of data (for saving methods).
Invariably, the logging wouldn't be sufficient for some problem, so they'd add more, re-deploy, etc, etc. Of course, since "branching is too hard," this also means that potentially broken code is checked in, so it could be deployed to test.
These web services were part of a webapp solution. So, I put a 'Test' area in there, and built some views to let them pick the API method they wanted to run, displaying some inputs appropriate to that method, and throwing the results up on the screen. Allowed me to debug the code in VS instead of having to read logs, and test locally.
These guys looked at me as if I was from the moon. Sigh.
|
|
|
|
|
Definately VS Code 
|
|
|
|
|
|
VS Code is really useful, especially without any of the addins. I use it as an editor for C/C++, C#, Java, Javscript, PHP and Python. I use simple batch files in the terminal Window of VS Code to build and run the samples.
|
|
|
|
|
|
I've always liked LINQPad - The .NET Programmer's Playground[^], ever since I heard of it anyway.
It's meant for giving you a C# oriented way to query different databases, but I find it great for just trying snippets of C# code.
*Not at all associated with the developer other than that we live in the same city and he gave an interesting talk a conference one time.
|
|
|
|
|
yeha <3 LINQPad, we got the Premium License. isnt that expensive compared to other tools or 3rd party components. And realy usefull..
I use it kinda every day, trying some simple stuff I'm not 100% sure how it works, testing some new things without creating that usual console application and .Dump() to view anything on the fly 
|
|
|
|
|
I vote for LinqPad also. A quick way to check out code snippets, classes and even small programs. Works with C#, F#, SQL and even VB. Similar debug methods as Visual Studio.
|
|
|
|
|
Have you tried Notepad++ with the CS-Script Plugin
Who the f*** is General Failure, and why is he reading my harddisk?
|
|
|
|
|
For C or C++ code, I use vim and gcc on Linux console.
For quick prototyping, Lua (again, with vim, on Linux console).
|
|
|
|
|
What is wrong with emacs? 
|
|
|
|
|
The learning curve? I am not used to emacs.
|
|
|
|
|
Yes it is a bit of a challenge, but so much better than vim once you get used to it.
|
|
|
|
|
emacs is a good OS, but it could really use a decent editor...
|
|
|
|
|
There's nothing wrong with three finger shortcuts.
|
|
|
|
|
Ctrl-Shift-S; "save all" in Visual Studio - a habit that a lot of us have.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Indeed! The problem starts when you have to bring in some fingers from the neighborhood...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
Quote: emacs is a good OS, but it could really use a decent editor...
This is a good joke, but it could really use a punchline
(The first time I heard this joke was in '92, so I've had quiet a long time to think of a reply)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
