Wild overwhelm Stars 6-1 to open playoff series



Minnesota Wild celebrates 6-1 win over Dallas Stars

Matt Boldy had two goals with an assist, Joel Ericksson Ek scored two power-play goals and rookie goalie Jesper Wallstedt stopped 27 shots in his postseason debut to help the Minnesota Wild beat the Dallas Stars 6-1 on Saturday in Game 1 of their Western Conference playoff series.

Kirill Kaprizov added a goal and two assists and Mats Zuccarello had three helpers for the Wild, who have lost nine consecutive playoff series since 2015. This was an impressive start in a long-expected matchup of Central Division rivals who finished behind Presidents' Trophy winner Colorado.

“A great stepping stone for us,” said defenseman Quinn Hughes, back after missing the end of the regular season with an illness.

“I think throughout the lineup tonight we came in and the guys were focused,” coach John Hynes said. “The thing I like is when we came in, I thought that we executed well. When it was time to check, we checked well. But I just thought we had the right mindset in how we need to play. And that was throughout the lines.”

Game 2 is Monday night in Dallas.

Dallas allowed the first goal in 15 of its 18 playoff games last year, and gave up three power-play goals in a 5-4 win over the Wild just nine days earlier.

The Stars trailed for good only 5 1/2 minutes into the series when Ericksson Ek scored on a pass from Boldy to make it 1-0. Ericksson Ek added another power-play goal past Jake Oettinger in the third.

Even though the Stars have made the West final each of the past three seasons, they are 1-7 in Game 1s at home during that span.

“I don’t even know what the record was coming into it,” said Glen Gultzan, who returned last summer for his second stint as the Stars coach. “The first period was tight, they executed on the power play. But we couldn’t get our game going at all in the second. I thought that they certainly, to a man, were better than us.”

Kaprizov and Boldy, the first Wild teammates with 40 goals in the same season, scored during a three-goal surge in the first 6 1/2 minutes of the second period for a 4-0 lead. Ryan Hartman scored in between, after having the primary assist on Kaprizov's goal.

Jason Robertson and Wyatt Johnston both had 45 goals as the first Dallas teammates with 40 goals in the same season. They combined on the Stars' power-play goal with 4:50 left in the second, Robertson scoring on a back-hander after gathering a pass from Johnston.

Minnesota went with the 23-year-old Wallstedt in net over playoff-experienced Filip Gustavsson, who in his playoff debut three years ago had 51 saves in a 3-2 double-overtime win at Dallas.

“He’s done a lot so far,” Hughes said. “I think we’ve got a lot of belief in both of those guys, and to be honest I didn’t think about it for a second. … We’ve got a lot of good pieces around here that keep everyone calm.”

Wallstedt's first NHL game was a 7-2 loss at Dallas in January 2024, but that was only one of five games he played for the Wild until this regular season, when he went 4-1 with a 1.82 goals-against average and .936 save percentage his last five starts. He also had four shutouts in a six-game span early this season.

The Wild still led only 1-0 with Dallas on the power play midway through the first period when Wallstedt, shielded and looking to the right of traffic, reached back to his left to make a glove save on a shot by Robertson.

Oettinger, who grew up about 30 miles from Minnesota's home arena, stopped 23 shots to open his 11th postseason series as the Stars starting goalie.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


What are the controllers and their types?

Salesforce controllers, also known as Visualforce controllers, are used to execute a set of instructions. Controllers specify what happens when a user interacts with the Visualforce Markup components such as Visualforce tags, HTML, fields, etc. When a user clicks on a button or link on a Visualforce page, the associated controllers will display the data related to the user action or component. The controllers have the ability to modify component behavior. They work on an MVC(Model-View-Controller) approach. Salesforce provides the below types of controllers.

  • Standard controllers
  • Standard List Controllers 
  • Custom Controllers

Wish to make a career in the world of salesforce? Start with HKR’S  salesforce online training !

1.Standard controllers

The standard controllers are the default controllers provided by Salesforce. They contain the same logic and functionality that are used for standard Salesforce pages. Every Salesforce object contains a standard controller that can be queried using the Salesforce Lightning Platform API. When a user interacts with a component on the page, the controller interacts with the database, fetches the relevant data, and displays it on the page. To display the relevant data on the Visualforce page, we need a record ID. So, we need to send an ID as a query string parameter in the page URL. The standard controller has a getter method that returns the record related to the query ID. If a user doesn’t have access to a certain object (or component) on the page, which is associated with a standard controller, it will display an insufficient privileges error message to the user. 

Associating a standard controller with a Visualforce page

To associate a standard controller to a Visualforce page, we have to use the “standardController” attribute on the tag. We should specify the name of any Salesforce object, which can be queried using the Lightning Platform API. Here is the syntax to associate a standard controller to a standard object on a page,

Salesforce Training

  • Master Your Craft
  • Lifetime LMS & Faculty Access
  • 24/7 online expert support
  • Real-world & Project Based Learning

2.Standard List Controllers

Standard list controllers are used for displaying or act on a set of records on the Visualforce pages. Related lists, list pages, and mass action pages are some of the examples of Salesforce pages that work with a set of records. The following are the objects that can be used with standard list controllers.

  • Account
  • Contract
  • Idea
  • Order
  • Product2
  • Solution
  • User
  • Lead
  • Opportunity
  • Asset
  • Campaign
  • Case
  • Contact
  • Custom objects

Associating a standard list controller with a Visualforce page

Associating a standard list controller is very much similar to associating a standard controller. In the standard list controller, we can set an object through the “standardController” attribute on the tag and then set the recordSetVar attribute on the same component. Here is the syntax to associate a standard list controller with an object on a page,

Once the standard list controller is associated, we can act on a set of records using expression language syntax. We can use a standard list controller to add pagination to a page with the help of the next and previous actions.

Cloud Technologies, salesforce-controllers-description-0, Cloud Technologies, salesforce-controllers-description-1

Subscribe to our YouTube channel to get new updates..!

3.Custom Controllers

Custom controllers are used to implementing custom logic and data manipulation for a Visualforce page. If we want to perform things like calling an external web service, validate and insert data, we can use a custom controller. The custom controllers override the existing functionality and implement customized navigation through an application. They execute entirely in system mode and users will have full control over the app’s logic. 

Create a Visualforce page that uses a custom controller

To add a custom controller to a Visualforce page, we have to set the “controller” attribute in the tag. When we use a custom controller, we cannot use a standard controller. Here is the syntax to associate a custom controller to a Visualforce page,

Controller Extensions

A controller extension overrides behavior in a standard or custom controller. Any Apex class with a constructor that takes a single argument of type “ApexPages” is referred to as a controller extension. We can implement the functionality of another controller to an apex tag while adding custom logic. Here is an example class for controller extension.


public class myControllerExtension {

//custom code

}

We can extend this controller extension on a Visualforce page like below.
Both the controller extension and custom controller use the action, getter, and setter methods. The custom controllers and controller extension classes ignore user permissions and field-level security as they execute in system mode. So, the custom controllers and controller extensions are mainly used to set organization-wide defaults. Based on the user profile, we can even define whether a user can execute methods in a custom controller or controller extension class. 

Salesforce Training

Weekday / Weekend Batches

Conclusion

Apex is a complete programming language that we can use to implement effective Visualforce pages. We can use Apex properties, which are a combination of a variable with getter and setter methods. We can implement anything on a Visualforce page with the help of controllers in Apex code. Using controllers, we can implement features like dropdown on a Visual page. They allow you to filter the records displayed on the page. While working with controllers, you should have an eye out for validation rules. You should be able to handle the validation rule exceptions. 

Related Articles:



Source link