Wikipedia talk:AutoWikiBrowser/Technical

see also Wikipedia talk:AutoWikiBrowser/Sources

Which command line svn?--93.223.170.90 14:32, 12 August 2010 (UTC)[reply]

So I downloaded TortoiseSVN and downloaded the AWB source. Having problems compiling the source using SharpDeveloper because I'm having problems installing Microsoft Windows SDK for Windows 7 and .NET Framework 4. (Maybe because I don't have Visual Studio installed?)

So I thought I'd try the Microsoft Visual C# Express Edition instead, but I think the link is outdated. Could someone please check on the link? Thanks! GoingBatty (talk) 00:15, 26 May 2013 (UTC)[reply]

Thanks to Bgwhite for updating these instructions! GoingBatty (talk) 23:59, 14 June 2013 (UTC)[reply]

Many thanks to Meno25 and Bgwhite for helping me navigate through my issues. Here are the steps I needed to go through to be successful in Windows 7:

1. Followed the instructions to install the latest version of TortoiseSVN and got the sources just fine.
2. Followed the instructions to install the latest version of SharpDevelop.
3. SharpDevelop gave me an error about Windows SDK, so I downloaded it from here and installed.
4. Installing Windows SDK gave me an error about .NET framework 4.5, so I downloaded from here and installed successfully.
5. Installed Windows SDK successfully. The installation wizard gives options to download several components - it is enough to download the component about .NET framework.
6. Ran SharpDevelop, clicked on File -> Open -> Project/Solution, and opened the "AutoWikiBrowser no plugins" solution file.
7. Got an error on AWBWebBrowser.cs stating "Error loading code-completion information for Microsoft.mshtml from Microsoft.mshtml: Could not find assembly file."
8. Here's where that "slight modification" comes in:

   • On the left hand pane in SharpDevelop, I opened the "AutoWikiBrowser 'folder'" and double clicked on "AWBWebBrowser.cs" to open it up in the edit window.
   • One line #2, I changed "using mshtml;" to "using MSHTML;" and saved the file.
   • On the left pane again under the "AutoWikiBrowser 'folder'", the first folder is "References". Expanded it.
   • The first item in the folder is Microsoft.mshtml in the title. I right clicked on it and deleted it.
   • Right clicked on the "References" folder and clicked on "Add a reference". A new screen popped up.
   • Clicked on the "COM" tab.
   • Scrolled down to find "Microsoft HTML Object Library". Clicked on it, clicked the "Select" button and "OK".
   • Under the "References" folder, a new line was now there called "MSHTML".

9. Compiled code and ignored errors.
10. Went to ...\AWB\AWB\bin\debug and copied AutoWikiBrowser.exe, WikiFunctions.dll and Interop.mshtml.dll from the folder to where I run AWB from.

Hope this will help others - thanks again! GoingBatty (talk) 23:59, 14 June 2013 (UTC)[reply]

Hi -- I am having trouble downloading the AutowikiBrowser source code. I am using http://svn.code.sf.net/p/autowikibrowser/code/AWB/ as the URL.

I get an "Unable to connect to a repository at URL" error.

Also I am having a problem registering WikiFunctions.dll -- Any help would be appreciated Sonofxavier (talk) 16:43, 24 January 2014 (UTC)[reply]

@Sonofxavier: Which software are you using to download the AWB source code? GoingBatty (talk) 13:20, 27 January 2014 (UTC)[reply]

@GoingBatty: it was a poxy setting. I didn't set the network poxy in TortoiseSVN -- thanks for that. I have the code know. However I am having problems with registering the WikiFunctions.dll on my Vista machine. Thanks for you attention.

SharpDevelop (latest version=5.1.0.5134_RC) requires .NET Framework 4.5 to be installed. I already have v. 4.0 Extended and don't want to install 4.5. --XXN, 16:34, 1 April 2016 (UTC)[reply]

Any way there could be a discussion on migration of the source repo to git rather than svn? How much effort would be involved? This is what I found via a quick Google search. http://stackoverflow.com/questions/79165/how-to-migrate-svn-repository-with-history-to-a-new-git-repository Shaded0 (talk) 19:26, 16 April 2016 (UTC)[reply]

I did the whole TortoiseSVN thing, then got to SharpDevelop and tried to open the AutoWikibrowser no plugin file, but it came up with

Can't load file AutoWikiBrowser no plugins.sln under C:\Users\---\Documents\AWB. Check the file permission and the existence of that file

Can someone help?--Mjs1991 (talk) 04:35, 18 August 2019 (UTC)[reply]

Internet Explorer will go out of support on June 15. AWB uses the Forms WebBrowser control which I assume still wraps the Trident rendering engine. Does anyone know whether the IE EOL means Trident will no longer be supported (I don't see anything in the docs), and whether it matters anyway? David Brooks (talk) 15:13, 7 May 2022 (UTC)[reply]

Someone on MSDN said that there will be no more security updates, and update "your" app to use WebView2. I explained it's not "my" app, and WEbView 2 isn't a drop-in replacement for WebBrowser. However, a developer at Microsoft said "the WebBrowser control will continue to work after the IE Desktop Browser end of life in 2022, until about 2029." Also, officially, Trident will continue to be supported. David Brooks (talk) 22:49, 16 May 2022 (UTC)[reply]

Another question is whether MediaWiki will support WebBrowser. With IE11 going out of support, MediaWiki will also become more and more incompatible with it, so eventually AWB will also have to switch to more modern alternatives. WebView2 is supported only on Windows 7+, which means dropping support increasing the minimum OS requirement from Vista on Wikimedia and XP on third-party wikis to 7, but with even Windows 7 being unsupported for almost three years (and given the lack of popularity of Vista), probably this is acceptable. —Tacsipacsi (talk) 14:59, 6 October 2022 (UTC)[reply]

I assume people interested in building the source can figure this out, but changes in Visual Studio mean:

• The latest editions are "Community", not "Express".
• The current download is VS2022 Community. On loading the AWB solutions, VS offers to auto-upgrade each project from Fx 4.5 to 4.8, or else download the 4.5 targeting pack. This doesn't happen if you still have VS2019 installed side by side; I noticed the new behavior when I removed 2019. The 4.5 option opens a webpage that is supremely unhelpful (4.5 is out of support, the only choice is "runtime" not "targeting pack", and I don't want to experiment for fear of polluting my repro). If AWB developers don't want to update the AWB projects, perhaps we should offer guidance on the alternative. David Brooks (talk) 18:58, 13 June 2022 (UTC)[reply]

After some digging, I still don't see a way of using VS2022 without upgrading all the projects, but if a new user still wants to build the current version, you can get VS2019 Community from here: https://visualstudio.microsoft.com/vs/older-downloads/. David Brooks (talk) 01:56, 14 June 2022 (UTC)[reply]

Two years later... I am setting up a new system, and found out that Microsoft has recently removed VS Community 2019. The paid versions of 2019 are still available, so I installed Professional (with a warning that an ARM64 platform is not supported), but it will presumably start nagging me soon for a license. Building the plugins also requires a download of Framework 3.5 (why?). I think it is time to upgrade the project files. David Brooks (talk) 20:58, 2 August 2024 (UTC)[reply]