Can T4MVC work in VB.NET? - vb.net

I've read around on this issue but I'm unclear if it's possible to get T4MVC working with VB.NET. I'm using T4MVC and ASP.NET MVC4.
I downloaded and installed T4MVCVB from this link and I've already installed the T4MVC package. I've renamed my helper from MVC to MVCH
My current problem is that when I try to use it within a View:
#Html.ActionLink("Home", MVCH.Home.Index)
I get this:
If I try to use it from a controller, such as:
Return View(MVCH.Home.Index)
It works no problem.
Has anyone been able to get T4MVC working with VB.NET?

T4MVCVB has not really been kept up to date with T4MVC, though I think it should still work. But note that when using it, you should not also import the T4MVC NuGet package. Instead, just use T4MVCVB by itself. I suspect that's why you're getting conflicts.

Related

MediaWiki: Getting "readapidenied" error instead of login token

That's a quite puzzling problem. I've multiple MediaWiki installations. In this specific case: Version 1.34.
Now I can login to all of these MediaWikis. Everything works fine.
Now I can access all of these MediaWikis via API --- EXCEPT ONE. The strange thing is: All of them are configured almost identical. I even copied the configuration from one wiki where everything was working to the second wiki.
To be more precise. If I send ...
/wikiA/api.php?action=query&meta=tokens&format=json&type=login
... I get a very reasonable answer, e.g.:
{"batchcomplete":"","query":{"tokens":{"logintoken":"37ec2e690eeb48a10ac66b2ccbca2b576000f9f4+\\"}}}
If I send ...
/wikiB/api.php?action=query&meta=tokens&format=json&type=login
... I get the following answer, e.g.:
{"error":{"code":"readapidenied","info":"You need read permission to use this module.","*":"See http://xxx.xxx.xxx.xxx/wikiB/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."}}
This can be reproduced using any web browser.
Q: What could be the reason that on this wikiB I even can't access the normal login module? It can't be the configuration. It's almost completely identical. It can't be the source code. I ran a diff on the PHP files and found no significant differences. What could be wrong here? It seems it must be something with the database. But how do I approach this? Does anyone have an idea? I would appreciate it very much if you could help!
I analyzed the data base: No difference. I did more research using google: And found a bug report.
It's a bug in MediaWiki. They provided an official software release with THAT kind of bug.
It turnes out there is a 1.34.0 version and a 1.34.1 version. My WikiA has 1.34.1 while WikiB had 1.34.0. After copying this one single file includes/api/ApiQuery.php from WikiA to WikiB and everything worked fine.
https://gerrit.wikimedia.org/r/c/mediawiki/core/+/580097/

Problem while editing symfony FOSUser (The option "mutiple" does not exist. Defined options are: )

so I faced this problem while trying to edit the FOSUser bundle on my symfony 3.4 project that I am working on using PHPStorm.I added roles hierarchy that is suitable to my project requirements.
But I found this problem that is stopping me from moving forward and continuing my project.
Any kind of help would be much appreciated.
PS: I added photos of the security.yml and RegistrationFormType.php as well as the problem encountred while executing on the navigator (chrome).
Post an answer because i cant add a coment yet. Change 'mutiple' to 'multiple' in 'roles'

Azure mobile app with existing sql backend

I have been following these examples in a previous stack overflow example, I need to convert to an Integer id to an Azure mobile app, and need a MappingDomainManager class described by user Kiske1 in the post below.
Azure Mobile App using existing database
However, I have been unable to complete this as Automapper.impl.PropertyAccessor is “Type of namespace Impl does not exist…” I am using the latest Automapper dll v6.1.1.0.
Does anyone know where PropertyAccessor has been moved to/or replaced with?
Also, both examples that were specified in this post are from 2014, does anyone know of a more up to date walkthrough and preferably an example project?
Does anyone know where PropertyAccessor has been moved to/or replaced with?
I searched at AutoMapper project and found that PropertyAccessor has been removed. Also, I checked my mobile app project and the Automapper version is 3.3.1, the PropertyAccessor exists and the old sample could work. I assumed that you could try to downgrade the version of your Automapper to fix this issue.
does anyone know of a more up to date walkthrough and preferably an example project?
For Automapper 6.1.1, the usage for FindTypeMapFor method and the parameter type for GetExistingPropertyMapFor method have changed, you could modify your code under SimpleMappedEntityDomainManager as follows:
var m = Mapper.FindTypeMapFor<TModel, TData>();
m.GetExistingPropertyMapFor(new PropertyAccessor(typeof(TData).GetProperty("Id")));
To
var m = Mapper.Configuration.FindTypeMapFor<TModel, TData>();
m.GetExistingPropertyMapFor(typeof(TData).GetProperty("Id"));
Moreover, you could refer to adrian hall's book about The Domain Manager.

Why do my T4MVC generated links have "Area=" when I do not use or define areas?

Using ASP.NET MVC 4 and T4MVCExtension 4.0, I generate a link with #Url.Action(T4Controllers.EnhancementList.ByVotes()) and get http://localhost:1025/Enhancements/EnhancementList?Area=. Any ideas on how to get rid of that extra-ugly url parameter?
Note: I thought of titling this "Areas? We don't need no stinkin' Areas."
Mostly the same as T4MVC #Url.Action(MVC.Controller.Action()) Renders "?Area=" Parameter in QueryString. Though I thought that was fixed earlier. What T4MVC version are you using?

Can I use/adapt the Kohana userguide module to create help pages for my application?

I'd like to create a userguide for the application I'm building using the Kohana framework, and I'm wondering if there's a way I can use the Kohana userguide module for this purpose.
I understand how to add userguide info for new modules that I create, and how to include my classes in the API, but I want to build a second, separate userguide for the actual application user, as opposed to the app developers.
At first, I thought I'd just try adding app help pages to the main userguide at APPPATH/guide. I tried adding a "application/guide" directory, and put a file in there called menu.md, but that just ended up replacing the Kohana menu in the userguide. After renaming the file to menu.myapp.md, it doesn't show up at all.
So then it occurs to me that I could simple edit modules/userguide/guide/menu.md to add sections for my app, and likewise add markdown files for each app component. But really it would be much better to have a completely separate userguide for app users since the Kohana documentation isn't relevant for them.
What's the best way to go about this? Should I create a duplicate of the entire userguide module and modify the routing, &c.? Or is there some way to set up both userguides using the one version of the module? Or am I barking up the wrong tree altogether? Is there some other module/approach that would be better for building "Help" pages for the app?
Thanks in advance for your help!
Yes, you can make docs for your application with the userguide. If you want examples, check out these links:
https://github.com/zombor/Auto-Modeler/blob/master/config/userguide.php
https://github.com/zombor/Auto-Modeler/tree/master/guide/auto-modeler
Note that you'll still get "api docs" and everything else, unless you change the config to hide them.