#VisualStudio's code analyzers are powerful, but maybe you want Roslyn to help make sure your code meets your style guide.
Let @meziantou show you how to write your own analyzer: http://msft.social/J4FN52
Yeah, I think most of the image handling should be made static.
Giving this a go:
using (var ms = new MemoryStream())
{
((Bitmap)source).Save(ms, System.Drawing.Imaging.ImageFormat.Png);
var image = new BitmapImage();
image.BeginInit();
ms.Seek(0, SeekOrigin.Begin);
image.StreamSource = ms;
image.EndInit();
image.Freeze();
return image;
}
IIRC the whole "load them into bitmaps" thing was due to problems/misunderstandings of how image sources worked... we got that sorted out since, didn't we?
> No luck yet. Did a clean install of MS Office on 2 computers, the installed RD. Still getting same behavior on both . Is it possible that the OS is the problem? I participate in the Windows Insider Program and am running Build 18312.rs_prerelease.190104-1630.
if the DataContext is set to your ViewModel instance, then just try the following:
<Border Visibility="{Binding Converter={StaticResource BossVisibilityConverter}}">
Also, you might want to look into a DataTemplateSelector
public class PersonDataTemplateSelector: DataTemplateSelector
{
p...
> No luck yet. Did a clean install of MS Office on 2 computers, then installed RD. Still getting same behavior on both . Is it possible that the OS is the problem? I participate in the Windows Insider Program and am running Build 18312.rs_prerelease.190104-1630.
namespace House
{
class Outside : Location
{
public Outside(string name, bool hot)
: base(name)
{
Hot = hot;
Name = name;
}
private new string Name { get; }
private bool Hot { get; }
override public string Description => Hot
? "It's very hot here. " + base.Description
: base.Description;
}
}
@MathieuGuindon It's meant to be a constructor, what am I doing wrong?
Ah OK, so if you keep inheriting from classes in a "chain" then I must pass all the arguments that are required by all the constructors along the chain
@MathieuGuindon maybe remind the spanish guy, too?
I'm thinking of just merging Comintern's work on CE into the next and let people play w/ pre-release then offiicaly release 2.4 on weekend before we merge any other PRs?
I haven't profiled it yet, but I don't think they were leaking anything. Everything that mattered was already static. We were needlessly churning converter objects though.
I wonder if I could get the severity counts on the toolbar ala the VS error window...
I still think that a comparison using == is usually more appropriate since whatever somebody overriding that operator deems equal to null should be considered unusable.
The main problem there is that most people override the operator do it wrong, us included.
The override in the SCW is borked because it is not symmetric.
If a wrapper w is wrapping a null reference you get w == null -> true and null == w -> false.
I have a ton of code blocks for autofiltering a report and applying a value to the SpecialCells(xlCellTypeVisible) range. It does the job, also quickly, but I just would like to truncate it wherever possible so I could lessen the strain during any debugging period.
With P_Template.Worksheets("S...
if the DataContext is set to your ViewModel instance, then just try the following:
<Border Visibility="{Binding Converter={StaticResource BossVisibilityConverter}}">
Also, you might want to look into a DataTemplateSelector
public class PersonDataTemplateSelector: DataTemplateSelector
{
p...
I have a ton of code blocks for autofiltering a report and applying a value to the SpecialCells(xlCellTypeVisible) range. It does the job, also quickly, but I just would like to truncate it wherever possible so I could lessen the strain during any debugging period.
With P_Template.Worksheets("S...
VBA Rubberducking
VBA Rubberducking