It can be hard to work out exactly where the problem is via visual studio directly. You can use the following to leverage msbuild and get more accurate information.
From a cmd prompt run:
msbuild /verbosity:d > build.txt
Tuesday, June 19, 2018
Fixing build issues
It can be hard to work out exactly where the problem is via visual studio directly. You can use the following to leverage msbuild and get more accurate information.
From a cmd prompt run:
msbuild /verbosity:d > build.txt
Thursday, June 14, 2018
Testing XPath
If you write XPath it is helpful to have a quick way to test what you are doing. You can give it a try using an online tool XPathTestBed. This is pretty easy to use.
If you are doing XPath on page source you can use the Console built into Chrome or Firefox and get immediate results. Just F12 to get into the developer tools. Go to the Console, and enter the following to get all div tags for example.
$x('//div')
Very useful and easy to use.
If you are doing XPath on page source you can use the Console built into Chrome or Firefox and get immediate results. Just F12 to get into the developer tools. Go to the Console, and enter the following to get all div tags for example.
$x('//div')
Very useful and easy to use.
Monday, June 11, 2018
How to use Google to find unsecured web.configs
I can't believe how easy it is to find web.config that are not secured. Put this into Google and you will be amazed at what you will get back.
inurl:ftp inurl:web.config filetype:config
or
inurl:http inurl:web.config filetype:config
Imagine if any of them have passwords in them.
inurl:ftp inurl:web.config password
or
inurl:http inurl:web.config password
inurl:ftp inurl:web.config filetype:config
or
inurl:http inurl:web.config filetype:config
Imagine if any of them have passwords in them.
inurl:ftp inurl:web.config password
or
inurl:http inurl:web.config password
Subscribe to:
Posts (Atom)