danwagnerco / selenium-vba

Automatically exported from code.google.com/p/selenium-vba
1 stars 0 forks source link

Selenium VB.net "NuGet Package" #141

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Operating system and version (32/64bit) : 64bit
.Net Framework version : 4.5
Office name and version(32/64bit) : 2013 32
Browser name and version : PhantomJS 
SeleniumWrapper version : v1.0.23.0

What steps will reproduce the problem with a public website ?
1. open Visual Studio 2013 
2. Project Properties then click on "signing"
3. Check on "sing the assembly" then choose New from the drop down menu
4. Rebuild the project
5. you will get an error "Unable to emit assembly: Referenced assembly 
'SeleniumWrapper' does not have a strong name"

What is the expected output? What do you see instead?
To build the project Normally after signing it with a strong Name

Please provide any additional information below.

First of all "selenium-vba" works GREAT with VB.net, but it will be awesome to 
just add the Package easily using NuGet, just like importing selenium in C#

The only problem is that i can't "Build the project with a signed assembly" 
while "SeleniumWrapper.dll" is in the reference files
I also tried to import the source code in this project but it still don't work, 
I get the same error but for 

Referenced assembly 'WebDriver' does not have a strong 
name    C:\Users\aa\Documents\selenium-vba-read-onlywc\trunk\wrapper\CSC 
SeleniumWrapper
Referenced assembly 'Selenium.WebDriverBackedSelenium' does not have a strong 
name    C:\Users\aa\Documents\selenium-vba-read-onlywc\trunk\wrapper\CSC 
SeleniumWrapper
Referenced assembly 'ThoughtWorks.Selenium.Core' does not have a strong 
name    C:\Users\aa\Documents\selenium-vba-read-onlywc\trunk\wrapper\CSC 
SeleniumWrapper
Referenced assembly 'WebDriver.Support' does not have a strong 
name    C:\Users\aa\Documents\selenium-vba-read-onlywc\trunk\wrapper\CSC 
SeleniumWrapper

Thanks a lot for the Great tool !

Original issue reported on code.google.com by yeha...@gmail.com on 5 Mar 2015 at 9:36

GoogleCodeExporter commented 9 years ago
All the referenced Dll need to be signed to sign a project and it's currently 
not the case.
Why don't you build the project unsigned?

Original comment by florentbr on 6 Mar 2015 at 6:27

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
That's my company’s policy, i must sign the project
And i want to integrate selenium to check some info in our servers

Original comment by yeha...@gmail.com on 6 Mar 2015 at 8:27