** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD **
10-25-2018
, 04:53 PM
Also the damn convention is curly brace on the next line. And the code lens by default in VS code makes a bunch of lines for itself. And the output/terminal window opens up below the code by default.
It's like the goal is to show as little actual code as possible in an ever-shrinking periscope view. I do not get it. I always want to see as much code as possible.
This is the big argument for indentation-based language btw. No wasted lines or characters, no arguments about curly braces or indention size (unless it's not 2). No curly brace matching hell. No space-wasting mario floating stairway ascii art when a bunch of nested curly braces close at the same time.
FWIW - my goal is not to convert the files but just make them appear to me as 2 space indents. So the flow would have to do something like convert all 4-space to 2-space while I view it, then convert it back when I save.
Last edited by suzzer99; 10-25-2018 at 04:59 PM.
10-25-2018
, 05:39 PM
10-25-2018
, 06:05 PM
Quote:
By the way, for the meat of the framework - namespaces, classes, methods etc - you want the .NET API Browser, as none of that stuff is specific to C#. For C# syntax you want the C# Programming Guide.
Hit me up with any questions, it's the language I know best. I am sad on a daily basis that I have to write in Java instead at the moment. It's like having to write a novel in pidgin English.
Hit me up with any questions, it's the language I know best. I am sad on a daily basis that I have to write in Java instead at the moment. It's like having to write a novel in pidgin English.
- What do you use for C# unit testing?
- Is there something like javadocs for C#?
- For #2 would it use those annotation thingies (the stuff in square brackets that live above classes and methods)? Are they often used for other stuff? One of our existing code examples uses them to drive a swagger-like API documentation. I do generally like the idea of annotation as semi-living code vs. formatted comments.
- Is using var considered bad practice?
- Does using VS Code for C#/.net development make any sense - or does it have to be Visual Studio?
Oh yeah, is there any way around this redundancy?
Code:
public class Response
{
public object Payload {get; set;}
public string Message {get; set;}
public bool IsError {get; set;}
public Response(object payload, string message, bool isError){
Payload = payload;
Message = message;
IsError = IsError;
}
}
Also some of the examples I find seem to capitalize class variables (like this) and methods. But then some don't. Is there a convention?
Last edited by suzzer99; 10-25-2018 at 06:17 PM.
10-25-2018
, 07:36 PM
Quote:
Thanks dude. A few general questions:
Oh yeah, is there any way around this redundancy?
You kids and your static typing I swear.
Also some of the examples I find seem to capitalize class variables (like this) and methods. But then some don't. Is there a convention?
- What do you use for C# unit testing?
- Is there something like javadocs for C#?
- For #2 would it use those annotation thingies (the stuff in square brackets that live above classes and methods)? Are they often used for other stuff? One of our existing code examples uses them to drive a swagger-like API documentation. I do generally like the idea of annotation as semi-living code vs. formatted comments.
- Is using var considered bad practice?
- Does using VS Code for C#/.net development make any sense - or does it have to be Visual Studio?
Oh yeah, is there any way around this redundancy?
Code:
public class Response
{
public object Payload {get; set;}
public string Message {get; set;}
public bool IsError {get; set;}
public Response(object payload, string message, bool isError){
Payload = payload;
Message = message;
IsError = IsError;
}
}
Also some of the examples I find seem to capitalize class variables (like this) and methods. But then some don't. Is there a convention?
2) Yeah, you use XML. Details here.
3) Yeah the annotations (they're called attributes) are nice. They're not used for the default documentation, but they are commonly used for other things. For example, if you're writing a REST API you annotate methods with [HttpPost] or [HttpGet], which should be self explanatory.
4) No. Opinions differ. I presume you know that var is just syntactic sugar - the variable is still typed, the compiler infers the type. Using actual untyped variables (with "dynamic") is frowned on.
Personally I avoid using var - the one time I use it is in ExtremelyLongTypeName x = new ExtremelyLongTypeName(); where if var is used you can still easily see what the type is reading the code. But Resharper (a VS addon which I recommend) by default has a style rule recommending the use of var, so like I said, opinions differ.
5) I haven't used VS Code yet so it's hard to say, but VS is pretty good.
6) You don't have to write a constructor if you don't want to, you can set properties with an initializer:
Code:
Response r = new Response { Payload = payload, Message = message, IsError = isError };
10-25-2018
, 09:32 PM
