Maybe logstash could help! I know that the applications I am talking about are designed to trace a connection across the network so you can see the related logs from each system the connection passed through (Firewall, switch, proxy, endpoint)
@Hosch250 elastic search is open source, so it's free if you host it. You would only pay if you wanted to use their cloud backend. github.com/elastic/elasticsearch
@SimonForsberg I have an internal NuGet server where I am currently trying to make a company-wide set of organized code libraries. It seems that everyone has these generic tools they put in some toolbox that they copy to each project. The biggest hurdle seems to be organization and naming. #NamingIsHard because if people don't know about it they are going to write their own version of your tool
@MathieuGuindon if there is server side tooling missing you can contact your host (GoDaddy) and tell them what you need. Update framework, install .NET6, etc. If they don't give you shell access then they have to help you. Otherwise, just move to a host who gives you shell access.
@MathieuGuindon, when the day comes that RD2 is deprecated and RD3 is the main project then you could move RD2 to it's own branch. Then merge in the entire RD3 codebase into the main RD repo using --allow-unrelated-histories. It's not pretty but it would allow you to have this obvious shift in the history where 3 comes in.
"olewoo itself is a C++ DLL so it is 32-bit only but because it's only used as part of the build and not the actual deployment, it should not prevent you from building 64-bit Rubberduck that can be consumed by 64-bit Excel. "
16>C:\DEV\GitHub\Rubberduck\Rubberduck.Deployment\Rubberduck.Deployment.csproj(49,5): error MSB4062: The "RubberduckPreBuildTask" task could not be loaded from the assembly C:\DEV\GitHub\Rubberduck\Rubberduck.Deployment\..\Rubberduck.Deployment.Build\bin\Rubberduck.Deployment.Build.dll. Could not load file or assembly 'olewoo, Version=1.2.6710.37528, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contai…
I'm trying to export a TLB file for a F# DLL. For .NET Framework up to 4.8 the following custom build command works:
<Target Name="PostBuild" AfterTargets="PostBuildEvent">
<Exec Command=""$(TargetFrameworkSDKToolsDirectory)\tlbexp" /verbose "$(TargetPath)"" />
<...
VBA Rubberducking
VBA Rubberducking
I'm trying to export a TLB file for a F# DLL. For .NET Framework up to 4.8 the following custom build command works:
<Target Name="PostBuild" AfterTargets="PostBuildEvent">
<Exec Command=""$(TargetFrameworkSDKToolsDirectory)\tlbexp" /verbose "$(TargetPath)"" />
<...