I've never even heard of this before.

Notes: these are two different ASP.Net projects. I didn't choose VB, the project was already existing.

A conversation between me and a senior:

Senior: (other module) still needs to develop (something you wrote)
Me: they should just use my code, it's compete and tested.
Senior: They should, but yours is in visual basic and they wrote their project in c#
Me: Ah, no problem, I will distribute it as a DLL for him.
Senior: No, I don't want to add dependencies
Me: ????
Senior: They will need to convert it to c# and add the classes

I stopped responding

Man............ what the hell

There should be a test or something in order to get the 'senior' status.

Our senior has blocked a hole project because it was going to use an API as communication between 2 projects. (The effort was already planned and both parties agreed)

2 weeks before execution, he (without notice) tells to not use an API (because he didn't know how or what it does) but use .txt files instead and someone has to manually export and import...

And here we are all setup, adding 2 months of work on a project for no extra value or reason...

So yeah.... what the hell

@Grumm I might slap him out of his office chair

the whole point of .net is the interoperability between all of it?
hell, you don't even need to compile and distribute it as dll yourself, they could just reference your project directly from their solution and it would compile together and stay up to date.

like... that's what it's for? ideally you would have one project which would be a library, something like SharedLogic, then the vb project referencing it, and the c# project referencing it, and i've never tried, but I bet you could even have two SharedLogic projects, one in vb, one in c#, both contributing to the same SharedLogic namespace, so whoever codes the bit of shared logoc they do it in the language of their project, and all the stuff from both languages would still be available to both projects under a single SharedLogic umbrella...

i mean... that's literally the point of the "solution can contain arbitrary number of projects, each in any of the supported languages, and each can be only remotely/partially linked, without the necessity to actually physically be fully present in the solution at all times"

oh btw, vb.net <-> c# automatic transpilers exist. fuck the boss, use one of those.

in fact, set up the SharedLogic project, only one, link it from both projects, and set it up so that on each commit or whatever, an automatic transpiler grabs all the appropriate stuff from both projects and transpiles them into F# or something.
triplefuck the boss XD