I am seeing an issue while scanning the Visual Studio code through fortify.
" Failed to translate the following 21 aspx files into analysis model. Please see the log file for any errors from the aspx precompiler and the user manual for hints on fixing those. "
All the aspx files are getting skipped. I see no precompilation errors while running.
VS version is 2010.
Please suggest what could be the issue.
Thanks!!
you have to give precompiled out in scan for that follow the below steps:
go to fortify.properties and uncomment this and set to false com.fortify.VS.SkipASPPrecompilation=false (by default it is true)
in compilation element in web.config file set the debug="true"
and then create a virtual directory of the web application and add it is as website to the solution. build the website once it successful then try the fortify scan again , it should work
Related
Got this error while building solution on CI server using VS2019 - 16.7.4
Any idea from where it could come from ? It doesn't happen all the time and only one solution. Can workaround by cleaning completely build working folder
CSC error CS7065: Error building Win32 resources : Arithmetic operation resulted in an overflow
First of all, please enter VS IDE, Tools-->Options-->Projects and Solutions-->Build and Run--> set MSBuild project build output verbosity to Detailed to get the detailed build log to locate the specific error.
If you use msbuild command line, you can add -v:detailed to get the detailed build log.
Then, try the following steps:
1) check every resource files, right-click on every that file-->Properties-->change its Build Action to Resource or Content`.
2) try to use Configuration Any CPU to build your project.
3) close VS Instance, delete .vs hidden folder, bin and obj folder and then rebuild your project again.
Besides, if the issue still persists, please share more detailed build log and description about the issue so that it will help us troubleshoot the issue quickly.
in my case, there was a weird combination of characters in the AssemblyInfo.cs
When I removed all these rubbish and changed that to
[assembly: AssemblyCopyright("Copyright © HP Inc. 2021")]
It built normal
I am in a real bind here. A programmer long before me made several applications in VS2010. We needed to move all these old applications to a file server so they can be backed up etc while awaiting updates. I am attempting to open this solution "Intranet". However, when I attempt this I receive the following error message:
\fs01\it$\Application-Source-Code\Projects-Important\Projects-Important\FFL Programs\Intranet\ :
error : Error opening web \fs01\it$\Application-Source-Code\Projects-Important\Projects-Important\FFL Programs\Intranet.
Unable to open the Web site '\fs01\it$\Application-Source-Code\Projects-Important\Projects-Important\FFL Programs\Intranet'.
The Web site '\fs01\it$\Application-Source-Code\Projects-Important\Projects-Important\FFL Programs\Intranet' does not exist.
We have a big customer coming in tomorrow morning and I need to take a look at the code to fix an error "a master page error". However, I cannot open this using VS2017 Version Selector. I have attached a screen shot of the sln file into to help assist with a resolution.
Option 1:
Copy your code from your file server (VS2010) see if it is opening/working on your local dev machine (in VS2010 orvs2017)
IF NOT
Option 2:
Still you'll need the above project files, now...
Create a blank solution in VS 2017 (relative to your programming language i.e. C# or Vb.Net etc) - also look for target framework
Locate the project file(s) (for e.g. ".csproj" files for c# projects) one by one manually.
Try to build the individual project( should there be any missing assembly references) and followed by complete solution build.
#NBaua, My brain has been overwhelmed lately. I was attempting to open a project when I needed to open a website. I just went to File --> Open --> Website and all works. Thanks again.
So our TFS 2013 builds do everything correctly except report code coverage. I've seen similar questions here, e.g. TFS 2013 - No Code Coverage Results, but we've already tried the suggested fixes with no results.
UPDATE 1 — we've taken more steps to try to resolve this; here's the complete list:
Ensured Visual Studio Ultimate was installed on the build server
Tried setting the build definition's "CodeCoverageEnabled" to true as well as the "Code coverage is enabled" setting
Ensured the build was using the Debug configuration and that PDBs were being generated for the DLLs to be tested
Added a .runsettings file with the correct ModulePath included under <CodeCoverage> (verified in build log that the module path was being interpreted correctly; it would produce errors if we intentionally malformed it)
Checked in .runsettings file
Set build definition to "Custom" and pointed to .runsettings file
The build process itself works fine. We can get code coverage results when we build the project locally in the IDE. On the build server, both MSTest and NUnit test projects run fine, and we see pass/fail results as expected. The "No Code Coverage Results" message still plagues us though.
Update 2 -
Here is what we see in the run log:
Somebody suggested homegrown code-coverage calculator in https://stackoverflow.com/a/16198120/141508, but it'd be a crime to spend $150 bazillion-thousand dollars on TFS 2013 & VS Ultimate 2013 with MSDN and still not have this one basic function working.
Add a run settings file to source control. Set the tests to custom and point to the run settings file. More info on using the .runsettings file can be found on msdn: http://msdn.microsoft.com/en-us/library/jj159530.aspx
I was experiencing the same problem. My issue was with the ModulePath. The MSDN examples suggest you can just use the name of a target binary. That was not working for me. However, when I made the name a regular expression, it worked. I am also dumping build output into one folder so that pdb and other reference files are found. Hope that helps.
<ModulePath>.*Administration\.dll.*</ModulePath>
I am using local build server with Visual Studio online with a .runsettings file and I had exactly the same issue.
None of the trickery above helped, so I tested the build script on the hosted build controller and it worked fine, so I decided the problem must be the build server itself.
I changed the Build Service account from "Network Service" to a regular windows user account in the TFS Configuration Tool and now code coverage is collected. Note that this user will need access to the TFS build directories.
I found this question because I saw something peculiar on this article. (Look for the "Delay" setting that defaults to 60).
d. Add a new argument ‘Delay’, enter details as mentioned below
Name – Delay, Direction – In, ArgumentType-Int32, Default Value – 60
This argument is required to delay coverage check, so that required build details are filled up by the build agent, this delay varies from
system to system, in some cases this might not be required at all.
http://www.prowareness.com/blog/failing-build-on-insufficient-code-coverageblock-coverage-part-3/
Maybe try putting in a "delay" work-flow item in the template you are using.......
currently I'm trying to create an WebSetup Project for one of our ASP.net4/Silverlight-Web Applications using Visual Studio 2010.
I created the setup Project according to this tutorial, but when I'm trying to build the Setup Project (I did a build of the whole solution before), I get the following error:
Unable to build project output group 'Content Files from MyWebProject (Active)'
According to this and almost any other site I found, this error refers to items that are included in the web-project but missing on disk.
I checked all my projects twice, there is no missing file.
Are there any other solutions to this problem?
Other things I tried:
This post: I do have .xml Files accompanying our .dlls. I also removed the xml File from my project, but it didn't help either
This post: Setting the startup project to my web application changed nothing.
Both of the above Posts are from this thread on forums.asp.net.
I had this problem also. (Visual Studio 2010 Pro, .Net 4.0) I found the missing file using "Publish..." option. Right click on the web app. Up near the top of the menu (5th from the top for me) is "Publish...". Click that. I did "Publish method: File System". Publish fails for the same reason that building the setup fails. The difference is that when Publish fails, it gives an error message.
In most cases it's due to missing files.
Expand all your projects and check that none of them is marked with the Yellow Exclamation mark.
For web applications the usual suspect is config.web and more specifically the Debug/Release versions , click on the '+' next to the Web.Config and see if they are marked as missing.
Good luck
I have faced the same issue at my side. `
[how to resolve ERROR: Unable to build project output group 'Content
Files from XYZ.xyz (Active)]
so solution ==> as per my project resolution I was just removed the reference file same name as the reference shown in the error block as [XYZ.xyz (Active) ] from the WCFSetup project followed by clean with Rebuild the solution.
The problem will be resolved and .MSI, as well as .setup file, will generated
I have a problem which has received plenty of attention which, despite much googling, I have been unable to resolve. I have a Test Project attached to my Visual Studio 2010 MVC 2 Application. When I attempt to run my tests, I get:
"no tests were run because no tests are loaded or the selected tests are disabled."
Following this, I followed the instructions in these posts, to no avail:
MSTest: No tests are run because no tests are loaded or the selected tests are disabled = my GUIDs are right, and the assembly IS being built - I can see the file in explorer.
MSTest Not Finding New Tests = reopening the solution & rebuilding didn't result in any change
http://richallen.blogspot.com/2008/05/ms-test-re-enabling-ignored-tests.html = the tests do not even appear in the test list browser under "loaded tests"
Furthermore, the output console reports:
"Could not load file or assembly 'file://\shared\shared\IT\Development\TPS\TPS.Tests\bin\Debug\TPS.Tests.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)"
I have confirmed the build settings on the Test Project are the same as those for the main project (Any CPU targeted).
Therefore, is it a problem accessing the resource over network share? Otherwise, does anyone have a suggestion?
If you want to continue using a network share to host assemblies in .NET 4, you can change a Visual Studio configuration option to grant those assemblies full trust. You need to edit C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe.config and add the following line:
<loadFromRemoteSources enabled="true"/>
To the configuration/runtime element. This is described in (slightly) more detail at http://msdn.microsoft.com/en-us/library/dd409252%28VS.100%29.aspx. I would not recommend making this change without understanding the security implications of doing so, some of which are outlined in that MSDN article.
In general, though, I agree with the previous answer. Hosting Visual Studio projects on a network share is going to create a large number of problems for very little benefit.
Having your source code on a share is plain wrong (period) and will lead to all sorts of 'gremlins'.
Do yourself a favour, use Source Code Control and have a local copy of the source code. You will waste a lot less time, and as a bonus you will be able to track who changed what.
If you go with TFS, the Visual Studio TFS Branching Guide 2010 is a valuable resource.
If you use SubVersion, then the Red Bean Book is excellent.
I was running all local but still had the problem. I found that what caused it was removing an xml tag during manual editing.
add:
CodedUITest() inside of tag brackets
on the line immediately above your class where all your test methods are.
add:
TestMethod() inside of tag brackets
on the line immediately above your test methods you want to run.
build project and run.
I tried the following steps while encountering this problem and luckily the issue got resolved...
Close the solution and open the empty VS editor and Check out the testrunconfig file
Open the solution and under CodeCOverage column, uncheck and check the dll's available( these dll's would be having a warning symbol)
Rebuild the solution and now run the test cases.
Hope this resolves the issue... :)
I struggled with this for days, and didn't find the answer (for my situation) anywhere, so though I'd jot down my experience...
So I had the same problem, doing what I thought was local testing on a test project created locally.. (I'm a novice...) but returning the same error mentioned above : /
Anyway it seems that VS2010 had by default placed my project dir within the library folder, which was classified as network, subsequently all files within were 'unavailable offline'.
By moving my project dir to c:// my project files became index-able. (much to my relief!)