test compile mode versus production compile mode
-
In a vb.net 2010 application, I have a page_load section of code where I would like to know add extra code unless I need it. Basically if the application is in development or test compile mode, I would like the application to point to a test url. If the application is in production mode, I would like the application to point to a production url. From the page_load section of code, is there a way to knowwhat mode the applicaiton is in? If so, can yhou show me the code on how to accomplish this goal? In addition, if the application is in production mode is there a way to not have the development or test logic be accessed by the application? If so, would you show me that logic?
-
In a vb.net 2010 application, I have a page_load section of code where I would like to know add extra code unless I need it. Basically if the application is in development or test compile mode, I would like the application to point to a test url. If the application is in production mode, I would like the application to point to a production url. From the page_load section of code, is there a way to knowwhat mode the applicaiton is in? If so, can yhou show me the code on how to accomplish this goal? In addition, if the application is in production mode is there a way to not have the development or test logic be accessed by the application? If so, would you show me that logic?
-
What you supplied to me is a very good option that works! However on my application, there are the build options for: 1-Development, 2-Test, and 3-Production. Based upon my build options, can I write code the will select only '1-Development' instead of placing #debug in the logic. Or having #debug stand for 1-development? If so, would you should me the code for this?
-
What you supplied to me is a very good option that works! However on my application, there are the build options for: 1-Development, 2-Test, and 3-Production. Based upon my build options, can I write code the will select only '1-Development' instead of placing #debug in the logic. Or having #debug stand for 1-development? If so, would you should me the code for this?
-
Sorry but I do not understand what you mean. The
DEBUGdefine is automatically set by Visual Studio when you do aDebugbuild, and unset when you do aReleasebuild. You need to decide what you want for aTestbuild and create the appropriate settings.