|
Thanks.
I spent the whole evening yesterday playing with various cross framework compatibility (.NET Standard 1.6, .NET Core, .NET Framework, Xamarin iOS, Xamarin Android, UWP) and I have the feeling the whole thing is... unfinished...
For example, .NET Standart 1.6 is compatible with an, as of yet, unpublished version of the .NET Framework!
Or my .NET Standard 1.6 library was correctly linked into Xamarin Android but had post compile error (creating debug info) with Xamarin iOS, and some method threw NotImplementedException when run on Android.
Anyhow it looks like one will have to wait for .NET Standard 2.0 for better compatibility story, which, last year, they said should be around VS2017 release date....
|
|
|
|
|
Agreed. The rate of improvement and the expansion of the knowledge base will be proportional to the rate of adoption; unless one is adventurous ... or someone else is paying for the adventure.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
|
I will have to wait for 2.0...
Not only tooling and compatibility should be better. But they will have a mechanism in place by then to access the native framework as well... wonder how it will work (they just mention it, but it's not available yet)
Thanks anyway!
|
|
|
|
|
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
|
|
|
|
|
We can't tell either: you need to read the error message carefully and do what it says.
It tells you exactly what you need to do to get the actual error report to be visible - message, stack, the whole enchilada. Do what it says, and it will tell you which file, which line is caising a problem, and what problem has been detected.
But until you have that, nobody can fix anything.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
If "your" code crashed the "server", who is at fault then?
You? Or the server for not anticipating your code? Both?
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
i am looking for guidance or best practice to review my code or review my colleague code working in same company.
two way i guess exist to review code. one is manual process and one should be automated process where people may use various tools to review code.
so please discuss two different process called manually review code and automated way review code using tools.
please guide me in details. thanks
tbhattacharjee
|
|
|
|
|
For automatic reviews, you can use FxCop and StyleCop. For manual reviews, you really should search the web for manual review processes, read them and agree with your colleagues on the best approach to conduct reviews; that's partly going to depend on your code cycle workflow (do you review pre commit to Source Control, or do you do it post commit and in a separate review stage for instance). We can't really help you that much on that side.
This space for rent
|
|
|
|
|
"Review" for what?
How do you measure "success"?
Machine learning involves calculating "distances" from some "ideal".
You need to "classify" your problem (i.e. what are the "measures") before you can achieve anything meaningful.
Unless you actually have some "good code" as a reference and for "training" purposes, you will get nowhere.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
Do you know what control can add photos and text horizontally as an attached file, when clicking on add button will put the image into the box, if the cell does not have image, insert the image in the horizontal box, if any. Horizontal cell is inserted into the new cell line. You see the attached image file. [IMG]http://imagizer.imageshack.com/img922/2316/JSa9oK.jpg[/IMG]
|
|
|
|
|
There is no ready-made Control which does exactly what you want.
I suggest you create a UserControl which has for example a Button and a ListView (and perhaps something more) and you write the code needed for your requirement ...
|
|
|
|
|
If it is a website you are building, have a look at Metro UI as a framework. They have some very nice controls for doing what you describe.
|
|
|
|
|
A StackPanel with the Orientation set to Horizontal; or a WrapPanel.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
Could you tell me I know StackPanel and WrapPanel it belongs to Visual Studio ? I did not find StackPanel and WrapPanel in Visual Studio.
|
|
|
|
|
They are used in XAML applications such as ones built by WPF.
This space for rent
|
|
|
|
|
In WinForms, use a normal panel. Drop some smaller panels in there with align=left, and it would fill from left to right.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Dear Experts
Following not a big Thing, I'm more asking where I'm missing the logic.
a.) Example which compiles
public void OutExample_03(out int outValue)
{
outValue = 0;
try
{
}
catch (Exception excpt)
{
Debug.WriteLine(excpt.Message);
}
}
b.) Example will not compile.
Message: The Out Parameter 'outValue' must be assigned before control leaves the current method.
public void OutExample_04(out int outValue)
{
try
{
outValue = 0;
}
catch (Exception excpt)
{
Debug.WriteLine(excpt.Message);
}
}
Does the Compiler assume for b.) that also enter the "try section" could not happen?
Thank you very much for your comments in advance.
[Edit]
VS 2013 Express.
modified 19-Jan-21 21:04pm.
|
|
|
|
|
|
Thank you very much for this. I read that link already, but a confirmation from you helped a lot.
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Again me
On the other hand
public void OutExample_03(out int outValue)
{
DoAnythingBefore();
outValue = 0;
}
does also compile, so I really don't see the logic why try catch will be handled Special.
It is like it is
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Because at Compile-Time the Compiler doesn't know if the Try-Cath COULD be succesful or not. It only recognized that there is a possibility for not-assigning the variable ...
|
|
|
|
|
Because, as already explained, the try block can terminate before the variable has its value assigned. In this case the catch part will be called and the method returns, but the value of outValue is indeterminate.
In the case above it is assumed (by the compiler) that one of two things will happen:
1. The method completes successfully, in which case outValue will have been correctly assigned.
2. An exception occurs, in which case the method will not complete, so the value of outValue does not matter.
|
|
|
|
|
Let me give you an example that might clarify it for you.
public void ThisIsaReallyStupidThingToDo(string input, out int value)
{
try
{
if (string.IsNullOrWhiteSpace(input))
{
throw new ArgumentNullException($"The value of {nameof(input)} must be set");
}
int.TryParse(input, out value);
}
catch (Exception ex)
{
}
} So, if you pass in an empty string, value will never be set because you bypass it completely and hit the exception handler. That's why you have to handle value outside the try/catch.
This space for rent
|
|
|
|
|
Thank you for your Feedback.
Yes all of this I'm aware. But it is not a real Explanation why
{
outParam= ..
} vs.
try
{
outParam= ...
}
will be handled different. I don't see a chance that in the sequence "try{ outParam= ..." something strange can happen.
Anyway it is more a philosophical thing not a real Problem.
Thanks again for your Feedback.
modified 19-Jan-21 21:04pm.
|
|
|
|