Optional parameters in VB.Net

Here's the situation. My ASP.Net Application has 3 projects A, B and C. B contains a function (ex: testfunction) that is used by pages in and C. Now for a specific requirement for Project C I need to make changes to the test function. To do this, I added an optional parameter with a default value that was passed in from C. I compiled my code and moved it to a server that was a Dll from B and C. In my testing, this requirement worked fine. But when the part of the application that project A is involved in calling the test function was caused by an error (method not found). I couldn't figure out why A should break. I just recompiled the DLL from A and moved it to the server and the error went away.

My question is, why did I have to compile the DLL from A when I didn't change the way I call from A?

+3
vb.net asp.net


source to share


No one has answered this question yet

See similar questions:

215
The definitive guide to API changes in .NET.
7
Does adding optional parameters to method signatures increase and does a method exception throw an exception?

or similar:

405
Is there a conditional ternary operator in VB.NET?
171
Could not find resources suitable for the specified culture or neutral culture
sixteen
Changing the C structure in VB.NET
8
C # DLL not working when used in vb.net project
five
When my large ASP.NET site is updated, IIS needs to recompile it a lot. Is there a way to significantly reduce compilation times?
2
ASP.NET MVC Entry Point
2
VB.NET reference interface in different assemblies without recompilation?
1
Run a program that is part of a large package from an ASP.NET web page
0
Calling a Fortran subroutine from VB.NET
0
Visual Studio is looking for DLL in the wrong directory



All Articles
Loading...
X
Show
Funny
Dev
Pics