> The EncapsulateFieldRefactoring potentially leaves large blocks of blank lines in the scenarios when the user elects to encapsulate numerous fields by wrapping them in a UDT. Residual newlines also occur in the MoveCloserToUsage refactoring and quickfix. It is less noticeable since these actions delete declarations one at a time. But, running the refactoring/quickfix against many declarations in the same module can potentially result in a large block of residual blank lines. To...
accomplish the newline removals, this PR introduces an IModuleRewriterExtensions class in Refactorings.Common. The purpose of the extension methods are to provide a convenient mechanism to clear residual newlines left behind by the removal of variable and member declarations. IModuleRewrite.Remove does not remove the EndOfStmtContext which can result in orphaned newlines. The extension method related to variable declarations also correctly handles removal of a variable declaration list...
in the scenario where are all variables in the list are identified for removal. (calling IModuleRewrite.Remove on each variable in a list leaves the VisibilityContext behind)
This PR modifies the default property RHS parameter IdentifierName. The previous default ('value') creates casing issues(#5552). The PR proposes to resolve the issue by using a custom parameter IdentifierName for each generated property of the form "propertyIdentifierValue". (e.g., `Property Let Foo(ByVal fooValue As Long)`).
Don't know if you are aware but if you have Chrome with extension IDon'tCareAboutCookies, the modal you've got on your homesite doesn't display, instead just non-clickable gray background. chrome.google.com/webstore/detail/i-dont-care-about-cookies/…
@SonGokussj4 oh hi! I tried to ping you on Twitter a few weeks ago - if you can update the CZ translations this week we'll have it merged in time for 2.5.1 release.
Hi! I am following some AWESOME tutorials about OOP for beginners from the Rubberduck blog and I found this: "Check the wrap fields in private type box" and "Select all". I'd love the feature but I am not able to see the checkbox in Refator->Encapsulate Field dialog (2.5.0.5244 version), only Is it (still) existing option in Rubberduck?
@RafałB. I'd strongly suggest you run with the pre-release builds. The "green" release cycle, despite best efforts, is sporadic at best (which is what happens with busy people who do this in their spare time for free).
I've rarely had an issue so bad with a pre-release that I've had to revert back, and, on those few occasions, it was a simple matter to run the installer for the earlier version that wasn't broken.
The only issue with that now is that there's a nag screen that lets you know that there's a newer version, however, I believe that version check can be disabled if it ever becomes that annoying.
I'm passing in a parameter that's supposed to set a project.param that should tell me which DB to attach to, but I've got that screwed up so it's not actually changing the server instance it's connecting to.
@MathieuGuindon well... there's my problem!
So, even though I'm running in Prod, it's loading to my Dev instance
I'm looking at an older SSIS pkg I wrote and it was long enough ago that I'm not seeing where/how I connected the variable to make it talk to the different db instance.
It may not help that the older, working pkg was written in VS '17 and I wrote the new one in VS '19 and they're just different enough that I'm struggling to make the 1:1 comparisons.
@MathieuGuindon between you and @this, you're the ones who convinced me that SSIS was the best way to go to load a CSV file to the server!
runs VS update to avoid thinking about the problem for a few more minutes
I've got this working in one place, but not another. Can you point me in the right direction of where I should be looking to see why/how I've managed to use the parameter correctly in one package, but not the other.
Unfortunately, either there's enough difference between VS17 & VS19 that I wasn't able to duplicate it properly, or I'm a complete moron and just skipped that section.
I can't even find, though, where I'm making the assignement in my VS17 project.
and, since I don't know the scoping rules well enough, I'm trying to keep unique variable names. ;)
I think the issue is here. This is the flat file connection manager from the working VS17 package
once I properly got everything working for that one, the file name seems to have gone away, but it works. I cannot get it into this state for the new, non-working package.
wait. no, that's not it.
on this loader, the input flat file was changing names depending on what client it was.
Here are the 2 Project.params set ups. The red arrows point to the non-working one (on my laptop in VS19) and the green arrows point to the working one (on my desktop connected via RDC in VS17)
I just don't know where I've got that Database parameter being used to connect to the correct server
I have created a working VBA script that allows the user to select a workbook and make a values only copy of it without opening it. This is useful for getting data from a workbook that is very slow to open. From here: https://stackoverflow.com/questions/63398348/how-can-i-copy-the-values-only-fro...
These are the environment properties showing the "Value" for the parameter I'm passing into the Database parameter I've set up for my SSIS packages.
The 1st & 3rd listings are for the production environments, the 2nd is development.
The 1st is for the prod on a different package which works properly in Production, while the 2nd & 3rd are for this package that seems to run in Dev no matter what I do.
I noticed that the GUID in the package name seems to be identical for all three. It would make sense that it's the same for the 2nd & 3rd, since they're the same package, but not that they'd match the first one, since that's a different SSIS package.
I'd say this is the issue except that it does run in Dev!
I also noticed that the Initial Catalog for all three is "ReportingDev", which I would think would be wrong, except the 1st one works just fine that way.
VBA Rubberducking
VBA Rubberducking