Because no codebehind or codefile file was found

Which version of framework are you using? If you are not able to add that from design view.. Copy Code. Posted Sep pm MalikRizwan. Posted Sep am MalikRizwan.

Please see the below link which may help you. Posted Sep am NMehta Add your solution here. OK Paste as. Treat my content as plain text, not as HTML.

Existing Members Sign in to your account. This email is in use. Do you need your password? Submit your solution! When answering a question please: Read the question carefully. Understand that English isn't everyone's first language so be lenient of bad spelling and grammar. If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem.

Insults are not welcome. Downloaded an extension called "File Nesting". When I build I add the generated feature file as an existing item, then I nest it in the feature file using the extension.

I needed to "Show All Files" in Visual Studio to see the code behind file at a sibling level to its associated Feature file this used to be an associated child file of the feature file in the previous Specflow version. I also need to use the "Include In Project" context menu item on the code behind file for it to show up in Visual Studios "Test Explorer".

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow.

Learn more. SpecFlow codebehind file generated but not attached to feature file Ask Question. Asked 2 years, 3 months ago. Active 1 year, 11 months ago. Viewed times. This leads to the following error: System. ConfigurationErrorsException : Configuration system failed to initialize System.

ConfigurationErrorsException : Unrecognized configuration section specFlow. CasHil CasHil 19 2 2 bronze badges. Have you installed the Specflow VS plugin marketplace. NET uses a ProjectName. ClassName structure for the Inherits attribute value. In the Visual Studio. In Solution Explorer , click to expand the Bin folder. The assembly that is generated when you compile the project from the previous section which is CodeBehindSamples.

In Visual Studio. The label is populated with the following value:. If your code-behind class files will be compiled on demand instead of precompiled, you must use the Src attribute to specify the relative path of the code-behind class file. Make sure that you include the actual class file when you use this method to deploy the application. For more information about potential issues when developing your applications in Visual Studio. NET with using the Src attribute, see the References section in this article.

Visual Studio. NET is designed to take advantage of precompiling your application code into an assembly instead of using the compile on demand approach that is described in this section. To add a new Web Form that is named SrcSample. NET, follow these steps:. To simplify this example, delete the Global. This is only done in this example to prevent additional errors that are related to the code-behind page of the Global.

Because you want the code-behind class file for this sample to compile on demand, do not build the solution now. If you followed the steps that are listed in the Use the Inherits attribute with precompiled classes section, you must delete the assembly in the Bin directory of the application before you follow the rest of the steps in this section. For more information, visit the Troubleshooting section of this article.

Otherwise, if you are using Visual Studio. NET , the code-behind page will be precompiled into an assembly that is located in the Bin directory by default.

After viewing the page, you will receive an error message that is similar as below:. This error occurs because the code-behind class file is not yet compiled, and you have not yet included the Src attribute to reference the code-behind class file.

The Src attribute is listed with the relative path of the code-behind class file SrcSample. Remember, do not build the solution because you want the code-behind class file for this sample to be compiled on demand. At this point, the page should be loaded in the browser, and the label is populated with the following value:. You may receive an error message that is similar to the following if you precompile your application in Visual Studio.

NET and then try to apply the compile on demand approach by using the Src attribute:. Keep in mind that the directory names following YourProjectName in the path that is listed in the error message will probably be different because ASP. NET automatically handles the building of the directories and their names. If you use the Src attribute, you must follow these steps to resolve the issue that is associated with the error message:.

Delete the YourProjectName directory that is referenced in the error message. You may also have to run the iisreset command from the command prompt before you complete this step.