This repo contains the foundational libraries that make up the .NET Core development stack.
Our mechanism worked fine without browser for now (POSTing username and password, and reading the CookieContainer for the token in the reply is easily done), but we're adding MFA (TOTP, FIDO2/U2F and Recovery Codes), and expecially the FIDO2/U2F stuff is rather tricky to implement on the client side, we better want to rely on the proven code in the browsers there :-)
@alealpha2000 maybe what is the issue?
I want to add a background image with a transparent dropshadow to a form in winforms. i managed to draw the background with UpdateLayeredWindow but now I'm stuck since apparently you have to draw the controls inside the form into the bitmap that is drawn with UpdateLayeredWindow
can't you at least use WPF, since that has waaaaaaaaaaay better support for that kind of stuff?
A background image with a transparent dropshadow on top of a solid background color can be done with the form's BackgroundImage property IIRC.
If you want see-through, you're in for a world of pain from what I remember making Windows Forms controls work on top of Aero glass.
I basically had to reimplement drawing and animated fades from scratch, calling into uxtheme's BeginBufferedAnimation etc
anyway i have another more important issue
i changed the backgroundimage of a user control in the visual studio designer but when i build and run the app the old backgroundimage is shown. i tried removing the old background image from resources, deleting the old background image file, deleting the .vs folder, deleting the /bin and /obj folders nothing worked
It's definitely plausible that the image got added to project resources or form resources more than once.
i have one final issue. i am making a custom button. i can't detect when the button is hot or pressed to change how it is drawn
private void SimulateTransparency(PaintEventArgs pevent)
{
//simular transparencia
var graphicsContainer = pevent.Graphics.BeginContainer();
pevent.Graphics.TranslateTransform(-Left, -Top);
var paintEvents = new PaintEventArgs(pevent.Graphics, Bounds);
base.InvokePaintBackground(Parent, paintEvents);
base.InvokePaint(Parent, paintEvents);
pevent.Graphics.ResetTransform();
pevent.Graphics.EndContainer(graphicsContainer);
}
protected override void OnPaint(PaintEventArgs pevent)
{
int radius = 5;
SimulateTransparency(pevent);
pevent.Graphics.SmoothingMode = SmoothingMode.AntiAlias;
Color fillColor, textColor;
if (AccessibilityObject.State == AccessibleStates.HotTracked)
{
fillColor = ControlPaint.Light(BackColor);
textColor = ForeColor;
}
else if (AccessibilityObject.State == AccessibleStates.Pressed)
{
fillColor = ControlPaint.Dark(BackColor);
textColor = ForeColor;
}
else if (!Enabled)
{
fillColor = ControlPaint.LightLight(BackColor);
textColor = ControlPaint.Light(ForeColor);
}
else
{
fillColor = BackColor;
textColor = ForeColor;
}
using (var path = RoundedRect(ClientRectangle, radius))
using (var backBrush = new SolidBrush(fillColor))
using (var frontBrush = new SolidBrush(textColor))
{
pevent.Graphics.FillPath(backBrush, path);
pevent.Graphics.DrawString(Text, Font, frontBrush, ClientRectangle, stringFormat);
if (Focused && ShowFocusCues)
{
var rect = ClientRectangle;
rect.Inflate(-radius, -radius);
ControlPaint.DrawFocusRectangle(pevent.Graphics, rect, ForeColor, BackColor);
}
}
}
If all you need to track is the hot state and there is no subrange of the control pixels to worry about, MouseEnter/Leave setting a private
isHot variable should do the trick.
@alealpha2000 Instead of Graphics.DrawString, consider using the TextRenderer class. That gives better ClearType rendering.
TextRenderer.DrawText does not take a StringFormat object
See https://stackoverflow.com/a/6404811 for a nice full comparison too.
I just got a new PC with a high resolution display and the the same binary app displays ToolStripComboBox and ToolStrip both display very unexpectedly. The height of the MenuStrip and ToolStrip is much large and the ComBox is displaying as a list box.
There have been some improvements, but I've never found a good strategy for DPI flexibility with winforms.
Jeremy Kuhne wants to tackle the issues it has eventually: https://youtu.be/m-NdyJVBf2Y?t=1388
Jeremy Kuhne wants to tackle the issues it has eventually: https://youtu.be/m-NdyJVBf2Y?t=1388
@jnm2 forgot I was the video. I will fine some bugs.
Hi guys. I'm having problems with FileSystemWatcher locking directories, so have been looking for alternatives. I've come across the PollingFileSystemWatcher here in the dot net source browser, but can't find any reference to it in the official docs. I see that the class has been around in the corefxlabs repo for quite some time, does anybody know if this is ready for use and if so, where I can find the binaries to reference?
*ready for use!
Hi all, I have a short question, and I hope this is the right place to ask it:
It is about the C# 8 nullable feature. Is there a way to mark a referenced library or nuget paket as "null-oblivious"?
Because I have the "Nullable"-feature enabled and I really like it a lot. Sadly most of the packages I am using did not implemente nullable awareness yet.
It is about the C# 8 nullable feature. Is there a way to mark a referenced library or nuget paket as "null-oblivious"?
Because I have the "Nullable"-feature enabled and I really like it a lot. Sadly most of the packages I am using did not implemente nullable awareness yet.
I building a library and packaging it as NuGet package, then when I use it in an application, the exceptions from the library doesn't show up the line numbers, I have try to include the PDBs in the NuGet package but still not luck, is there a way to get the library line numbers when printing exceptions from an application that uses the library NuGet package?