-
Notifications
You must be signed in to change notification settings - Fork 486
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TestStack.White.WebBrowser NuGet package not published #158
Comments
Silverlight support is not provided by Jake, author of this package, so he is hesitant to release the WebBrowser packge. |
refer this #134 |
Hey guys, It's not that I don't want silverlight support, its that I personally do not have the time to maintain it and look into issues. I barely have enough bandwidth to help people with White normally at the moment (am on a sabbatical in the UK so I have less time than normal). I am happy to help anyone (via skype?) get up to speed on the White codebase and for them to help me maintain White, especially the Silverlight support. If someone or a few people stepped up, then I can setup the NuGet packages and release them within a day or two. This is an open source project, and Silverlight needs someone from the Community to step up :) |
Closing this issue in the absence of a silverlight champion for White |
Oh, I should mention. I will be tagging releases in the White repo AND you can download the WebBrowser NuGet packages from my build server (http://teamcity.ginnivan.net). I am in two minds about just publishing the Thoughts? |
You can release the webbrowser package. People can use the WebBrowser and On 21 January 2014 18:33, Jake Ginnivan notifications@github.com wrote:
"ಬೇರೆ ಭಾಷೆಗಳನ್ನು ಗೌರವಿಸಿ, ಆದರೆ ಕನ್ನಡವನ್ನು ಮಾತ್ರ ಪ್ರೀತಿಸಿ, ಕನ್ನಡದ ಉಳಿವಿಗಾಗಿ |
I tried to write Silverlight UI Tests but the required TestStack.White.WebBrowser NuGet package is not published yet. Is there any reason why?
See: http://www.nuget.org/packages?q=teststack.white
BTW: tagging the git repository as it relates to a release might help too. ;-)
The text was updated successfully, but these errors were encountered: